Getting up to Speed with JS Today
summary
Shows why using a framework solves server-fetching, rendering and edge deployment pain by demoing an Express server that uses renderToPipeableStream to server-render a React app and fetch data on the server instead of leaking tokens. Compares React and Solid with a 10,000-item component to show signals avoid massive re-renders unless React uses memo. Demonstrates Qwik’s lazy-splitting with dollar-sign markers and the predictable one kilobyte runtime that delays JS until needed.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 1:04Front end trends overview
- 2:29Web components and BFF concept
- 3:53Backend for frontend explained
- 6:21Why use a framework
- 7:44Building a framework demo
- 9:31Server rendering basics
- 12:28Data fetching on the server
- 15:17Fine-tuning performance with reactivity
- 17:01React vs Solid JS demo
- 20:12Front end becoming invisible
- 20:56Quick framework deep dive
- 24:23UI tools landscape recap
- 26:56React Forget and future
- 28:43Choosing the right tool
- 30:48Wrap-up and key takeaways
related talks
21mReact Server Components
34mReact The Good Parts
27mAnd Now You Understand React Server Components
20mSpeeding Up Your React App With Less JavaScript
28mImproving Performance using React Server Components!
38mSOLID JavaScript
25mFrontend is dead, long live full stack
17mSupercharging React Performance with JavaScript Signal Optimisation