The state of frontend frameworks in 2023
summary
Shows concrete demos and measurements: a hand-rolled Node server using render-to-pipeable-stream to stream React, client bundle ~1MB and server bundle ~2MB, Reddit example loading 3.2MB of JS and taking 13.6s, a 10,000-element list benchmark comparing React (needs memo) and SolidJS signals, and a Qwik-style demo where closures marked with $ are code-split so interactivity loads on demand resulting in an 1 kilobyte initial payload claim and lazy-loaded click handlers. Actions, tools, sizes, and which approaches work or require workarounds are all shown.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:00Title
- 2:00Frontend vs backend
- 3:30BFF
- 6:15Backend value proposition
- 8:40Cloudflare workers
- 9:40Frameworks
- 10:55Exercise
- 12:40ServerJS
- 20:45React
- 23:10Demo
related talks
29mNew Trends in Front-End Development (and What We Can Learn from them)
29mQuo vadis, frontend?
33mRendering on the Web: Performance Implications of Application Architecture
27mFacing Frontend's Existential Crisis
22mPerformance Empathy
32mWhat's Happening in the JavaScript Ecosystem?
41mLow-budget JavaScript: composable frontends that are fun and friendly
17mSupercharging React Performance with JavaScript Signal Optimisation