The Inevitability of the Thin Client
summary
Discusses the costs of heavy JavaScript bundles (network and CPU) and common mitigations like BFF layers, then proposes an alternative: execute application logic on the server to avoid overloading client devices. Describes how to build lightweight SPAs that include SSR, routing, and server push out of the box to eliminate many problems of modern JS apps.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:12History and philosophy
- 7:40Thin client concept
- 16:50Frontend architecture problems
- 18:13Koroyev library on Scala
- 32:02JavaScript in Koroyev
- 44:52Summary
- 48:46Q&A
related talks
38mThick client — does that mean slow?
29mDesigning very large JavaScript applications
37mMyths about "Thick" Clients
50mThe State of Server Side Java Webapps
31mBack to boring
37mRunning JS on the Server at Scale — What Can Go Wrong
33mRendering on the Web: Performance Implications of Application Architecture
28mServer-Side Apps, Not Server-Side Rendering: A Real Alternative to React