Out-of-Order Streaming — The Future of Web Development
summary
A clear claim: implementing out‑of‑order streaming lets servers render and stream sections independently so skeletons appear immediately while later pieces swap in. The demo builds a minimal system with Express + ReactDOM streaming, async server components rendered to template tags, and a ~10‑line custom element swap to replace fallbacks in the DOM. It measures no change in API latency but a visibly snappier UX, far smaller client bundles because only opted‑in client components ship, and the prototype works end‑to‑end.
AI-written summary · about
chapters (12)
- 0:00Out-of-order streaming intro
- 1:54Web rendering history
- 10:00Problems with single-page applications
- 11:25Reintroducing server-side rendering
- 13:35React server components
- 17:49Proven principles
- 18:10Demo: streaming basics
- 23:10Classical streaming limits
- 26:07Suspense for loading
- 32:33Out-of-order streaming
- 37:34Benefits of out-of-order
- 39:22Summary
related talks
26mProgressive HTML Rendering 101
31mStreaming React for Faster UIs
31mLiving on the Edge
58mUnderstand the Next Phase of Web Development
30mRendering the Future: Building a Dev-First Library With Streaming & Server Components
14mStreaming the Web (it's not what you think)
18mSplitting the Work: Streaming Server Rendering with Suspense
45mJavaScript Streaming - A Qwik glimpse into the future