Where the future is heading for JS Frameworks…
summary
Traces 30 years of web history and makes concrete claims: Signals reduce rerenders so components run once, Qwik streams tiny JS pieces and resumes on the client, and dynamic tree‑shaking plus gradual rendering can remove whole layout branches based on prop values. Describes Wix products used for experiments (Wix Dev Platform, Kodex visual IDE, Wix adless) and an experimental framework prototype. Flags a real security incident where a VS Code extension exfiltrated code and argues micro‑frontend isolation and compiler‑led optimizations are needed now.
AI-written summary · about
chapters (18)
- 0:00JS frameworks future
- 1:25Web frameworks past
- 4:43Websites vs web apps
- 5:29SSR and Jamstack 2.5
- 8:04React baseline framework
- 9:48React limitations and signals
- 11:34Signals future state management
- 11:55Framework streaming
- 13:40Declarative behavior locality
- 15:06Compilers in frameworks
- 15:48Gradual rendering
- 17:12Tree shaking potential
- 19:41Security challenges
- 20:44Micron frontends modularity
- 22:11Design to code
- 24:21Web essentials regulations
- 26:30AI impact on frameworks
- 27:34Q&A
related talks
53mThe Future of Frontend
58mKeynote: Where Web Tech is Going Now
18mA Brief History of Web Applications — Why the Qwik JS Framework Is Innovative
32mWhat's Happening in the JavaScript Ecosystem?
29mQuo vadis, frontend?
31mThe post-Jamstack world and the rise of Hybrid Frameworks
28mThe Future of JS Frameworks
49mQwik: Streaming JavaScript framework