You really don't need all that JavaScript, I promise
summary
The central claim is that many sites work better with less client-side JavaScript, backed by concrete numbers and demos: a static 8.5 MB HTML dump renders 200 ms faster than a React client rendering one tweet, server-side code highlighting transfers 10 KB less and keeps paint time virtually unchanged, and a docs prototype uses the portal element activates iframe navigation plus postMessage to preserve a left-pane scroll without an SPA. Portal is Chrome-only and buggy, and native CSS/HTML features like scroll-snap and datalist replace lots of JS.
AI-written summary · about
chapters (10)
- 0:00Performance matters
- 1:27The cost of heavy sites
- 5:11JavaScript dependency risks
- 9:07Developer complexity
- 12:38Reasons for frameworks
- 16:06Portal element demo
- 21:22Solving navigation issues
- 25:58Portals and state
- 30:14Progressive enhancement
- 35:55The future of the web
related talks
21mYou Really Don't Need All That JavaScript, I Promise
41mYou Really Don't Need All That JavaScript I Promise
49mThe Unbearable Weight of Massive JavaScript
53mThe Unbearable Weight of Massive JavaScript
32mStay Away From My Path!
31mBack to boring
32mResponsible Javascript
46mFrontend Minimalism in Action: Do More With Less JavaScript