Myths about "Thick" Clients
summary
Examines why so-called “thick” (client-heavy) web apps can be fast by tracing frontend architecture from two-way binding through one-way data flow and virtual DOM to reactive primitives and lazy work. Demonstrates Solid’s signals (automatic dependency-tracking signals+effects), surveys partial hydration/islands and streaming SSR, and explains Qwik’s resumability (compiler-split handlers into lazy chunks so HTML is interactive immediately). Recommends lazy computation and microstate to avoid wasted work and suggests experimenting with Solid or Qwik and splitting monolithic components.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:28What is a thick client
- 5:17JS rendering evolution
- 8:28Unidirectional data flow
- 11:59Bottom-up approach
- 15:52Rendering patterns
- 23:34Summary and future
- 27:26Q&A
related talks
38mThick client — does that mean slow?
21mQA
29mNew Trends in Front-End Development (and What We Can Learn from them)
28mIntro to Qwik: The Answer to Web App Scalability Issues
56mThe Inevitability of the Thin Client
49mJavaScript Streaming - A Qwik glimpse into the future
20mQwik
21mFROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM