We actually need more JavaScript frameworks
summary
Built a decision site called what the framework that initially fails but is later revised; it catalogs 23 JavaScript Frameworks and filters them by site type and SPA/MPA choices. Trying to serve a hybrid MPA exposes that only five candidates appear, with Next/Redwood left after filtering and 11t’s edge SSR limited to Netlify and experimental — concrete gaps. Cites experiments where SSR matches static speed and Twitter’s Flight and Twitter Lite pivots to justify the claim: more frameworks solve real, distinct tradeoffs.
AI-written summary · about
chapters (6)
- 0:00Introduction and frustration
- 1:04Changing my mind on frameworks
- 3:55Choosing frameworks is complex
- 6:50Evolution of server rendering
- 9:22Lessons from Twitter's journey
- 10:46Why we need more frameworks
related talks
57mA Survey Of JavaScript Meta-Frameworks
01h 02mChoosing a JavaScript Framework
47mJavaScript Frameworks: There Should Be Only One
57mJavaScript Framework Cage Match
45mDid We(b Development) Lose the Right Direction?
31mThe post-Jamstack world and the rise of Hybrid Frameworks
28mThe Future of JS Frameworks
45mNo framework frontends in practice - use the platform!