Resilience: Tried and tested approaches
summary
The core claim is that resilience comes from layering: pick the core functionality, implement it with the simplest tech (HTML/CSS/forms), then enhance with JavaScript, Ajax, WebSockets and Service Workers. Evidence: HTML grows from 21 elements to 121 because browsers tolerate unknown tags; canvas starts as Apple proprietary then standardizes; the first ARPANET message sends “LO” before crashing. Principles used are Postel’s robustness and Murphy’s Law; progressive enhancement proves practical — basic service always works, advanced features reward newer browsers.
AI-written summary · about
chapters (30)
- 0:00Intro
- 4:12Metcalfes Law
- 5:23hypertext transfer protocol
- 8:11HTML
- 9:39Longevity of HTML
- 11:00What the browser does not do
- 11:37How we grow
- 11:56Canvas
- 13:04Image Element
- 16:40CSS
- 18:15Objectoriented CSS
- 20:00Robustness Principle
- 21:55Imperative Languages
- 22:31Web Stack
- 24:19XML
- 27:06Error Handling
- 27:56Murphys Law
- 28:18Slow Charts
- 28:47We need to acknowledge this
- 30:55Step 3 Identify the core functionality
- 31:54Identify the core functionality
- 34:00Level 3 Enhancement
- 35:40Web Sockets
- 36:26File API
- 37:51Scale
- 40:16Its not realistic
- 42:15Its too hard
- 44:41My priority
- 45:19Tiny ponies
- 46:37Instant distribution
