Resumability in the next generation frontend framework With O1 loading time
summary
Compares measurable behavior: Qwik achieves O(1) startup by shipping HTML that serializes closures into a Qwik JSON blob so the browser resumes state without full hydration. Event handlers are referenced by QRLs embedded in HTML and lazy-loaded on demand; the Qwik loader is ~1 KB. Demo shows only clicked handlers and needed framework code download, and Qwik offers a qwikify path to reuse React components with rules about file separation.
AI-written summary · about
chapters (12)
- 0:00Resumability in frontend
- 1:09Hydration in frameworks
- 3:19Qwik O1 loading time
- 5:50Getting started with Qwik
- 6:10Live demo lazy loading
- 8:38Lazy loading under the hood
- 10:47Serialization and state in Qwik
- 11:08React in Qwik
- 12:12React + Material UI demo
- 13:59Rules for React in Qwik
- 14:22Qwik City overview
- 15:04Recap and future
related talks
48mResumability in the next generation frontend framework With O(1) loading time
15mThinking Qwik!
28mIntro to Qwik: The Answer to Web App Scalability Issues
21mQwik: web revolution by default
21mQwik: Performance is a Human Design Issue
20mQwik
25mGil Fink @ ReactNext '23 | Qwik-ifying React
34mQwik: performance as a human design problem