0kb JS and Back Again: Why Vite is the future of the MPA
summary
Web pages now ship about 500 KB median page of compressed JavaScript; a server-render-first approach with streaming and partial hydration cuts that dramatically. The team builds Marco — a server-side framework with streaming HTML and opt-in client islands — and benchmarks show Marco serving pages faster than comparable React builds; disabling partial hydration produces 2–6× more JavaScript on real pages. Modern tooling like Vite gives first-class SSR, tiny default config, and an embeddable dev server that makes this MPA-first workflow practical.
AI-written summary · about
chapters (7)
- 0:00Introduction to JavaScript growth
- 6:24MPA vs SPA trade-offs
- 8:50Marco framework origins
- 10:54Partial hydration benefits
- 12:40Vite’s role in modern tooling
- 15:29Vite community impact
- 16:32Closing and Q&A
related talks
20mVite - The Next Generation Frontend Tooling
25mThe Eternal Sunshine of the Zero Build Pipeline
52mVite Under a Lense
41mYou Really Don't Need All That JavaScript I Promise
01h 03mBetter performance === greater accessibility
33mRendering on the Web: Performance Implications of Application Architecture
31mFaster content websites via SSR and progressive hydration of Web Components
23mFuture of Nuxt and Vite