Back to boring
summary
Argues that many sites should be plain multi‑page HTML instead of heavy client apps, shows measurements: average page weight >2 MB, React docs 400k vs 50k without JS, and examples where static or server rendering wins. Describes tools and tradeoffs: server rendering, SSR → static builds, ISR and Netlify on‑demand rendering, Next.js accessibility fixes, Astro island architecture, Open UI primitives, shared element transitions; reports deploys taking 10–20 minutes and huge node_modules causing unnecessary complexity.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:11Left-pad incident and over-engineering
- 3:17Web’s growing complexity
- 8:59Trade-offs in web dev
- 10:44Server to browser shift
- 13:34Client-side navigation issues
- 16:25Pre-rendering and hydration
- 18:31Static generation delays
- 19:34React.js docs performance
- 22:04Accessible UI controls
- 24:51Progressive enhancement
- 26:38Shared element transitions
- 27:41Necessary HTML only
- 28:43Edge functions for speed
- 30:28Closing thoughts
related talks
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript
45mGive Me Back My Frontend!
45mDid We(b Development) Lose the Right Direction?
01h 14mJust Do Less
39mYou really don't need all that JavaScript, I promise
32mMake Websites, Not Apps
31mFaster content websites via SSR and progressive hydration of Web Components
54mPushing Pixels