QA
summary
The session claims concrete wins: signals-first primitives let reactivity be serialized so large parts of an app never need to run in the browser, Quick uses code extraction to avoid loading JavaScript into the VM, and Solid optimizes post-startup runtime cost. Demos show a Solid prototype of server-components style resumability and a Quickify tool that wraps React components as lazy hydrated islands. Practical trade offs surface: migration helpers exist but SSR and web components require special handling and add complexity.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:58What are your differences of opinion
- 6:27Can Quick get to the point of not needing to download the component ever
- 8:51How do we get started
- 11:57Web Components
- 14:07Drawbacks
- 18:21Future Projects
related talks
37mMyths about "Thick" Clients
20mQwik
28mIntro to Qwik: The Answer to Web App Scalability Issues
15mThinking Qwik!
49mJavaScript Streaming - A Qwik glimpse into the future
44mRethinking Isomorphic JavaScript with SolidStart
17mSupercharging React Performance with JavaScript Signal Optimisation
18mResumability in the next generation frontend framework With O1 loading time