Make it Resumable with Qwik
summary
Claim: Qwik makes pages resumable resumes server-rendered state in the browser so the client does not rehydrate whole component trees. It uses a build-time Qwik optimizer that extracts $ handlers into separate lazy bundles and splits the app into many tiny JS chunks. Demo shows a button whose onClick bundle downloads only on first click and an “agency” app with routes and server round trips that work with lazy loading and a service worker prefetch in production.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:41Core Web Vitals
- 8:46Big O() notation for frameworks
- 10:10The VM Metaphor
- 11:50Resumability = resume app
- 13:02Getting Started
- 19:36Qwik Components
related talks
48mResumability in the next generation frontend framework With O(1) loading time
21mQwik: Performance is a Human Design Issue
34mQwik: performance as a human design problem
18mResumability in the next generation frontend framework With O1 loading time
21mQwik: web revolution by default
20mSpeeding Up Your React App With Less JavaScript
20mQwik
25mGil Fink @ ReactNext '23 | Qwik-ifying React