There and Back Again: Grokking State and Data
summary
Compares using immutable values versus mutable references for UI data, showing how modeling data as entities (stable identities) versus values changes update surfaces and testing. Presents tiny implementations: an entity store with stable IDs, subscription functions that map component props back to source state to make updates efficient, and an example treating the browser address bar as an entity wired to views; examples integrate end-to-end with Redux/MobX styles and reduce boilerplate.
AI-written summary · about
chapters (8)
- 0:00State and data
- 5:02Documents to DOM
- 10:28Entities as values
- 15:45Temporary values
- 20:43Tracking events
- 25:19Subscriptions and updates
- 30:00Context and identity
- 31:26Q&A
related talks
52mState management beyond the libraries
18mState Management — One Meta-Model to Rule Them All
41mMobX, or: Going from Mutable to Immutable to Reactive State Management
30mTackling State in Angular Applications
25mEnemy of the State
41mThe Battle of State Management in modern frontend applications
27mReact, But For Data
28mPersistent data structures - good for UI