Qwik: performance as a human design problem
summary
Qwik claims to make performance a UX problem not a checklist by using resumability instead of hydration so pages load with no JS and individual interactions download only the tiny handler (demo: a button click pulls a single click payload). Qwik City provides file routing, apps stay interactive even with JS disabled, and Qwik reports O(1) scalability across component counts. Demoed image optimization rewrites assets from 1.7 MB to 29.9 KB. Partial hydration and islands require manual partitioning; Qwik automates it.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:08Why another framework?
- 3:14Developer experience vs performance
- 6:45Principle of least effort
- 9:15Performance as a design problem
- 10:40Qwik's philosophy and DX
- 13:50Hydration and its challenges
- 17:43Resumability and instant interactivity
- 20:15Systemic performance issues
- 21:00Live demo introduction
- 22:03Creating a Qwik app
- 23:30Zero JavaScript in development
- 25:14Interactive components without hydration
- 27:22Demo of a game built with Qwik
- 29:53Image optimization in Qwik
- 33:05Future projects and closing
related talks
21mQwik: Performance is a Human Design Issue
21mQwik: web revolution by default
20mQwik
48mResumability in the next generation frontend framework With O(1) loading time
15mThinking Qwik!
30mQwik Go For 100
18mResumability in the next generation frontend framework With O1 loading time
26mMake it Resumable with Qwik