The 100 year web
summary
The web succeeds because it combines existing services, is free to use and — crucially — uses declarative markup so browsers can interpret intent rather than bespoke code. That advantage erodes as HTML becomes procedural and browsers + JavaScript frameworks proliferate: HTML5 ballooned with bugs, frameworks create bloat (a single tweet can force ~1 MB downloads) and accessibility loss, and experiments show 1.1% lost enhancements for users without JS. Real deployments prove the point: one declarative rewrite cuts NHS hardware cost from £5 per patient to one penny per patient and replaces 70 developers with one.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:42100-year thinking in architecture
- 5:32Origins and simplicity of the web
- 8:02Declarative vs procedural approaches
- 12:18CSS and JavaScript evolution
- 15:25Consequences of JavaScript dominance
- 19:46Accessibility and permanence concerns
- 22:45Moore's switch in computing costs
- 25:36Declarative programming examples
- 28:44Real-world declarative success stories
- 30:32Conclusion and future outlook
- 31:15Q&A session
related talks
44mAdvancing the web without breaking it?
38mDear Developer, the Web Isn't About You
38mA short history of the web
46mKeynote:The Web:It’s just a tool though, isn’t it?No it’s not it’s an alien lifeform!
53mFrom HTML to here: The evolution of Web development and where we lost our way
38mOf Time And The Web
28mThe Future of the Web
45mThe Layers Of The Web