FROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM
summary
Claims that Qwik sends interactive HTML first then streams JavaScript on demand, demonstrated by a live app with buttons, a clock and a counter that only download and execute chunks when clicked. The demo uses a service worker cache, the $ compiler marker to create lazy execution chunks, resumability to replay state without full hydration, server functions and directory routing via Qwik City. The examples run and show reduced upfront JS and on-demand fetches.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:40Web performance matters
- 4:54SPAs and hydration
- 6:39Qwik’s paradigm shift
- 8:06Demo: resumability and streaming
- 12:47Lazy execution with signals
- 18:19Server functions refactor
- 20:49Summary
related talks
21mFROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM
18mA Brief History of Web Applications — Why the Qwik JS Framework Is Innovative
49mJavaScript Streaming - A Qwik glimpse into the future
20mQwik
47mFrom Zero to Qwik: Building Your First App with Confidence
49mQwik: Streaming JavaScript framework
21mQwik: Performance is a Human Design Issue
48mResumability in the next generation frontend framework With O(1) loading time