The Future of JS Frameworks
summary
Argument that single‑page apps were a mistake and the web is swinging back toward server‑first patterns, with concrete moves: React’s new compiler trying to match React compiler vs fine‑grained reactivity, broad adoption of Astro‑style islands and partial hydration, and more use of server components, resumability and signals. Examples include frameworks reusing old compiler ideas to slice server/client code, PWAs kept for native features, and many teams prioritizing developer experience and DX tools that reduce hydration and runtime JavaScript.
AI-written summary · about
chapters (6)
- 0:00Introduction and panel setup
- 1:23Future of JavaScript Frameworks
- 10:20Framework choice and ecosystem
- 14:53Progressive Web Apps discussion
- 19:15Server-side vs client-side rendering
- 27:02Closing thoughts and Q&A
related talks
53mThe Future of Frontend
27mWhere is the JavaScript world going?
23mThe Next Wave of Web Frameworks is BYOJS
58mAlways crashing in the same car (the state of front end web development in 2022)
32mWhat's Happening in the JavaScript Ecosystem?
31mThe post-Jamstack world and the rise of Hybrid Frameworks
23mThe Dawning of a New Age for Fullstack React
44mJavaScript in 2017: You might (not) need a framework
