Hunters and Gatherers
summary
A clear decision comes from specifics: John Harrison builds a marine chronometer that keeps time to within seconds per day and finally enables longitude after centuries of failed schemes; lunar-distance tables require armies of human “computers”; the 1707 fleet wreck kills thousands; immutable data and referential transparency let functions be evaluated in any order enabling parallelism; someone stores every interpreter stack and implements an undo debugger; SOAP becomes an evolutionary dead end. Strong opinions, weakly held guides whether to hunt or to gather.
AI-written summary · about
chapters (6)
- 0:00Start
- 14:31dead reckoning
- 28:27unexpected adaptations
- 35:58divergent evolution
- 40:40hunters and gatherers
- 46:06QUESTIONS & ANSWERS
related talks
24mOne Hundred Years of JavaScript
19mKeynote: We're Gunna Program Like it's 1999
01h 04mHow to outsmart time: Building futuristic JavaScript applications using Temporal
39mInvent the future, don't recreate the past
41mDownTheRabbitHole.js – How to Stay Sane in an Insane Ecosystem
49mBuilding a Time Machine with ES6 Proxies
51mWhat the Functional? What, How and Why
48mThe universe in a single arrow