Thick client — does that mean slow?
summary
Talk examines why single-page/thick-client web apps became common despite initial performance problems, and reviews recent framework-level solutions that improved client-side performance. It names JavaScript frameworks (the evolution of JS frameworks) as the technology area and analyzes framework fixes and recent approaches to mitigate slowness, concluding by answering whether thick clients are inherently bad.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:50Thick clients matter
- 5:40Thick client definition
- 7:50State management issues
- 10:19Bidirectional vs data flow
- 12:06Bottom-up state management
- 15:36Microstates and reactive managers
- 16:18Solid.js signals
- 18:03CSR SSR patterns
- 21:59Islands and partial hydration
- 23:28Resumability in rendering
- 27:20Fast thick clients
- 28:43Future of thick clients
- 31:30Q&A
related talks
37mMyths about "Thick" Clients
56mThe Inevitability of the Thin Client
01h 23mWhy Slow?
21mWhy are web applications slow, and what to do about it
01h 29mClient-Side UI Smackdown
16mNeed for Speed: How Modern JavaScript Frameworks Are Solving Web Performance
29mClient Says Your Awesome Web App Works Slowly. Now What?
38mThe Front-End Future