Why you don’t need a Single Page App
summary
Argues that full SPAs aren’t necessary by showing a Node.js server-rendered frontend (using tag-template literals and AsyncLocalStorage) that outputs HTML in 5–10 ms server render and ships a tiny client. Demo is a complete e‑commerce frontend built with nanoweb in ~2,200 lines, eight dependencies, and a real demo against backend APIs; client JS is just 53 KB JavaScript bundle (largest component 14 KB) and feels SPA‑like via morphdom and web components.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:01Recap about the History of Web Applications
- 2:44Downsides
- 10:25Nanoweb
- 11:27React Server Side Components
- 15:04Tag Templates
- 18:40Hotwire
- 19:34How To Fix the White Flashes
- 22:20Web Component
- 22:52Shadow Dom
- 24:07State Management
related talks
29mSPAs are dead. Long live Microfrontends.
31mRethinking composable E-Commerce Frontends
28mSingle Page Applications - was it a good idea?
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
39mYou really don't need all that JavaScript, I promise
33mGo Full Stack Server-Side Rendering vs SPAs
37mA Single Page Story
51mBuilding Amazing Single Page Applications the Right Way