Enemy of the State
summary
Compares three concrete approaches: server-rendered pages are effectively stateless on the front end but cause slow full-refresh UX; DOM/Ajax libraries (jQuery) bind UI events and quickly produce tangled inter-component listeners; observer frameworks (Backbone/Angular) move data into models but keep UI state in controllers so wiring explodes at scale. Recommends a Flux-style one-way data flow with central stores holding all state, giving predictable testing, easy serialization (Circle CI demo) and cheap undo/redo (Goya drawing example implemented in ~10 lines).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:00State Types
- 3:30Stateless
- 5:20ServerSide Rendering
- 5:50Ajax Rendering
- 8:10Observers
- 10:50Complexity
- 11:40Facebook
- 12:30Flux
related talks
58mFrontin' like a Back-er
24mEnemy of the State
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
30mReact: Rethinking best practices
38mThe Front End Architecture Revolution
34mFunctional UIs and Unidirectional Dataflow
31mApplying Unidirectional Data Flow Beyond the ReactJS Ecosystem
48mClientside templates for reactive UI