Architecting Web Apps - Lights, Camera, Action!
summary
Claim: the 45‑year‑old actor model maps well to the web and actually reduces main‑thread jank by breaking work into message‑driven actors. Tools and artifacts: an Actor base class plus a starter boilerplate, TypeScript message contracts, xstate for state machines, Preact for UI, and actors deployed to Web Workers or server processes via hookup/lookup. A stopwatch demo and production apps show it works: quieter main thread, easier testing, lazy code splitting, but it remains experimental.
AI-written summary · about
chapters (8)
- 0:00Intro
- 4:18Areas of Ownership
- 5:51Separation of Concerns
- 8:35Actor Model
- 14:52Location Independence
- 17:43Review
- 21:13Thoughts
- 23:47Wrap Up
related talks
38mThe Actor Model: a new mental model for React
27mActor Model in Javascript
45mEverything is an Actor
22mBuilding WebApps Like It's 1972 🧙♂️by Leandro Ostera
31mLet the Main Thread Breathe!
57mBeyond the buzzword: A reactive web application in practice
42mLet the Main Thread Breathe!
01h 13mWeb: The good parts