Server/Client unified execution model
summary
Claims that resumability replaces hydration by shipping a ~1KB bootstrap and pulling code on-demand actually works in the demos: buttons and counters show no client render logs until click, a service worker prefetches bundles, and a dollar-sign code extraction plus signals serializes state and subscriptions so events recover state without re-executing components. Server-side execution via a server-dollar export moves expensive work off-device. Limitations: nonserializable values (classes/instances) still break this model.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:49Websites failing Core Web Vitals
- 3:15Hydration problems in frameworks
- 5:44Partial hydration and RSC
- 7:29Resumability and Quick framework
- 10:19Signals and compiler optimization
- 10:59Quick framework basics demo
- 17:43State management with signals demo
- 22:00Dynamic code loading demo
- 25:10Lazy loading and server execution
- 32:10Streaming and progressive execution
- 33:54Q&A
- 37:43Quick adoption and future
related talks
30mA Nerdy Guide To The Web Trending Concepts
35mHydration, Islands, Streaming, Resumability... Me, Oh My!
24mUniversal Applications
49mQwik: Streaming JavaScript framework
39mTowards Universal JavaScript
32mHydration Islands Streaming and Resumability
21mHydration, Islands, Streaming, Resumability… Oh My!
09mThe Only Way to Eat an Elephant