Did We(b Development) Lose the Right Direction?
summary
A personal site is rebuilt from a universal-JS stack to plain HTML/CSS with tiny JS, yielding reduced page weight by 64% and build time 4min → 40s across ~400 pages and 20,000 monthly views. Examples cited: Netflix halving signup TTI by dropping React, 11ty median Lighthouse score 100, Gmail offering a 25k low-data mode. Problems highlighted: 340KB index.html with 22 inlined articles, 22 JS bundles, inaccessible client-side routing without live regions.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:53The state of web development 10 years ago
- 7:20How can it be so easy to mess up?
- 15:15Universal JS apps for content-sites
- 19:15What's the enhancement in the wild?
- 20:36Does this architecture improve UX?
- 22:15Are app frameworks apps after all?
- 24:03"Benefits" of client-side routing
- 26:46The foundation of the web
- 30:57The web loses quality
- 34:23Complexity is king! (but what for?)
- 39:56Outro
related talks
54mDid we(b development) lose the right direction?
43mAre We Building the Web the Right Way?
29mPreprocessors, Components, and CSS in JS or: How I Learned to Stop Worrying and Love the Website
38mDear Developer, the Web Isn't About You
55mReckoning: Frontend's Lost Decade
34mWe need to talk about the front web
49mBrowser Native Web Development: No Frameworks, Just the Browser
43mResponsive, Adaptive and Responsible