Understand the Next Phase of Web Development
summary
Demos show concrete patterns and working code: page-by-page server rendering with small client interactive islands, measured reductions from 64 full-file requests to single XHRs on form posts, and component-level streaming that turns a ~3s blocking load into incremental spinners using streaming server-side rendering and a custom ad-streaming-block patch. Navigation is upgraded by intercepting links and pushState (enhanced navigation). On the server side, WASI Preview 2 component model runs a Rust web server calling a C plugin and a Go markdown component via WIT interfaces; the multi-language pipeline builds, runs and serves HTML successfully.
AI-written summary · about
chapters (22)
- 0:00Welcome
- 1:30Web development evolution
- 5:23Server-first frameworks
- 6:05Next.js SSR demo
- 8:30Server-first rendering benefits
- 9:54Emerging server frameworks
- 10:36Streaming SSR explained
- 11:41React streaming demo
- 14:27Blazor streaming demo
- 18:37Streaming rendering internals
- 22:45Enhanced navigation UX
- 23:48Svelte navigation demo
- 26:36Blazor navigation & state
- 29:04Enhanced navigation guide
- 33:14Interactive islands
- 36:24Astro multi-framework
- 39:52Modern web UI trends
- 40:13WebAssembly on server
- 40:55WebAssembly history
- 43:23Component Model & WIT
- 45:48Multi-language server demo
- 57:24Q&A
related talks
58mKeynote: Where Web Tech is Going Now
22mThe (Abundant) State of the Web
30mJust another ECMAScript Trait Syntax ProposalStop breaking the web and start building server-rendered web apps using next.js
29mKeynote: Kent C. Dodds - The Web's Next Transition
16mStreaming Server Side Rendering simplified with Next.JS
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
24mServing content on the web: from PHP to RSC—and beyond
22mProgressive Enhancement