Qwik
summary
Qwik City is a meta-framework on Qwik that aims to ship very little to no JavaScript by using resumability instead of hydration, so the server serializes app state and the browser picks up without replaying code. Builder IO shows JavaScript optimization moves a site score from 36 to 96 in tests. Tools demonstrated include Party Town (third-party scripts in a webworker), service-worker + Cache API active prefetching, streaming SSR, file routing, request handlers and an optimizer that pre-renders static parts.
AI-written summary · about
chapters (13)
- 0:00Introduction to Qwik
- 1:03What is Qwik City
- 3:28JavaScript impact on performance
- 5:33Party Town for third-party scripts
- 6:54Qwik’s resumability vs hydration
- 10:45Qwik’s SSR-first approach
- 11:06Qwik City features
- 13:53Qwik City’s unique advantages
- 15:40Active prefetching in Qwik
- 16:43Streaming SSR in Qwik
- 17:44Hybrid static and dynamic rendering
- 18:46MPA vs SPA with Qwik
- 19:07Builder.io’s performance goals
related talks
48mResumability in the next generation frontend framework With O(1) loading time
21mQwik: web revolution by default
21mQwik: Performance is a Human Design Issue
28mIntro to Qwik: The Answer to Web App Scalability Issues
34mQwik: performance as a human design problem
49mQwik: Streaming JavaScript framework
21mFROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM
15mThinking Qwik!