Did we(b development) lose the right direction?
summary
Claim: heavy client JavaScript often harms users more than it helps. Evidence: a cutting‑edge personal site ships 340KB index.html with 22 inlined articles and performs worse than a 100%‑HTML vintage site; Netflix cuts time‑to‑interactive by 50% after removing client‑side React; a tinyhelpers HTML‑first site records TTI 1.4s on 3G; Gmail keeps a 25KB low‑resource mode. Tool notes: experimenters mention pre‑act, Next and static HTML tradeoffs. Surface numbers: only 6% use CSP and ~80% expose vulnerable deps.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:14Did web development lose the right direction?
- 13:37The same code runs on the server and on the client!
- 18:39Does this architecture improve user experience?
- 19:53Maybe app frameworks are for apps after all?
- 21:25"Benefits" of client-side routing
- 33:46The web loses quality...
- 40:00Your users don't care about your technical implementation.
related talks
40mDid We(b Development) Lose the Right Direction?
38mDear Developer, the Web Isn't About You
53mThe Long-Tail of Performance
39mGiving you ways to increase, but also explain site performance, to your boss.
49mIn a New York Minute
33mRedefining Web Performance
41mMake JavaScript Faster
48mBecome a Frontend Developer Ninja using HTML5, JS and CSS3