Ariel Shulman @ ReactNext '25
summary
Argues that React server components and SSR become necessary because client side rendering no longer scales as projects balloon, shows server components as a bundler feature that streams prerendered React fragments, discusses caching at build time versus per‑request streaming, names the Model Context Protocol and MCPUI for streaming UI from external tools, points out concrete costs like serialization limits and payload size, reports that the abstraction is leaky and recommends making server/client boundaries explicit.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:24SSR and React Server Components
- 2:27Web timeline of SSR
- 5:20Client-side rendering issues
- 7:52Rendering fails at scale
- 10:46React’s recursion limits
- 11:50RSC as a solution
- 13:38AI and streaming UI
- 16:34Text vs UI in agents
- 18:01Streaming React components
- 19:06RSC hidden problems
- 22:17Explicit server boundaries
- 23:45Summary and Q&A
related talks
51mDiscussion on React server components
59mReact Server Components Explained for Backend Developers
01mAurora Scharff, shares her excitement about React’s future
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
43mReact Applications on the Server
48mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: Fad or Real Progress?
21mReact Server Components