Resilience
summary
Argues for a concrete three-step method: identify the core functionality, implement that core with the simplest technology (HTML, lists, forms, images), then enhance with CSS, AJAX and service worker. Cites Postel’s Law and Murphy’s Law as reasons to prefer lax declarative layers and to assume failure. Points out surprising real-world bloat — NASA.gov ends up with 139 requests and 6.7 MB (roughly 3 MB of blocking JavaScript) to render basic text and images — and shows service worker works as an enhancement, not a substitute.
AI-written summary · about
chapters (7)
- 0:00Start
- 17:45Be conservative in what you send, be liberal in what you accept.
- 23:47Anything that can possibly go wrong, will go wrong.
- 30:06layout
- 41:01If you build pages with the idea that parts other than html are optional, you will create a better and stronger web page.
- 41:17developer convenience
- 41:34user needs
