Server-Side Apps, Not Server-Side Rendering: A Real Alternative to React
summary
Claims a full-featured app ships with ~10–14 MB bundle using React while a server-driven approach uses ~HTMX plus ~1 KB client JS, the HTMX runtime ~50–70 KB gzipped. Shows a production-style app (courses) rebuilt with server-generated HTML, progressive fetches, form posts and redirects, HTMX targets and fragment replacement, and gets 100 Lighthouse score out of the box. Demonstrates how form POST/redirect, hidden fields, and server-side validation preserve state, focus, and UX without heavy client frameworks.
AI-written summary · about
chapters (11)
- 0:00Server-side alternatives intro
- 3:58Why drop client frameworks
- 6:26No-JS to-do app
- 9:01Full-page rendering speed
- 11:53State management without client state
- 14:05Pure server-side limits
- 14:45Adding interactivity with HTMX
- 19:03HTMX size and simplicity
- 23:00Why not React
- 26:33Downsides and when to avoid
- 27:38Conclusion
related talks
40mThe state of frontend frameworks in 2023
08mLightning fast SSR React apps with top perceived performance and no (client side) JavaScript
44mServer Side Rendering from the trenches
41mYou Really Don't Need All That JavaScript I Promise
45mReact Server Components: Fad or Real Progress?
24mUniversal Applications
25mThe Costs & Benefits of React Server Components
01h 14mReusable Server Components in React Workshop