Did We(b Development) Lose the Right Direction?
summary
Argues that modern sites often ship unnecessary JavaScript — example site ships 22 JavaScript files and universal frameworks inline lots of data — causing median React pages to need ~10s CPU and Netflix to cut time-to-interactive by 50% when switching to vanilla JS. Shows rebuilds that work: a 11ty site scores 100 performance and an Astro island build drops a 250KB bundle to 10KB, reducing page weight by 64% and build time from ~4 minutes to 40s. Notes only 11% use CSP and ~98% of sites have detectable accessibility issues.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:45The state of web development 10 years ago
- 8:27How can it be so easy to mess up?
- 17:13Universal JS apps for content-sites
- 21:32What's the enhancement in the wild?
- 23:12Does this architecture improve UX?
- 24:53Are app frameworks for apps after all?
- 26:28"Benefits" of client-side routing
- 28:26We use too much JavaScript!
- 31:27The foundation of the web
- 35:33The web lost quality
- 38:41Complexity rocks! (but what for?)
- 42:04DX vs UX
- 44:08Outro
related talks
53mThe Unbearable Weight of Massive JavaScript
27mSlashing Performance Bottlenecks and Poor User Experience
41mHow we make Web Apps lightning fast at Microsoft!
01h 02mThe Wrong Kind of Fast: Embracing Evidence-Based Architecture
32mResponsible Javascript
58mResponsible JavaScript
52mOverboard.js
31mBack to boring