Resilience
summary
Argues that resilience comes from design choices not buzzwords: HTML and CSS are error tolerant so new elements like canvas picture and srcset add features without breaking old browsers, while client‑side JavaScript is fragile and needs defensive layering. Recommends a three-step plan: identify core functionality, implement it with the simplest technology (HTML/forms/images), then enhance with Ajax websockets local storage and service workers so features work even when things go wrong.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:03RESILIENCE
- 4:29gopher
- 9:14HTML tags
- 9:58HTML5
- 13:50img src alt
- 18:13selector property value
- 23:01declarative HTML
- 26:30XHTML 2
- 28:05JavaScript
- 32:372. Make that functionality available using the simplest
- 43:42Times New Roman Verdana
