One Hundred Years of JavaScript
summary
Argues that code must survive decades and centuries, citing Mocha (1958) still running for Department of Defense contracts and the longevity of COBOL and Flow‑Matic as evidence that cheap fixes beat rewrites. Calls out concrete failures: two‑digit years (Y2K), 32‑bit timestamp rollover in 2038 32‑bit rollover, and a 2 billion play counter overflow. Recommends practical patterns like CSS‑in‑JS / single‑file components that collocate markup and styles so systems can evolve.
AI-written summary · about
chapters (5)
- 0:00Intro
- 5:23Preserving Meaning Requires Continuous Change
- 8:15The Software Engineering Model
- 11:01COBOL
- 16:33Legacy Problems
