Mutable or Immutable? Why not both!
summary
Claim: MobX-State-Tree mixes mutable instances with immutable snapshots are plain JS objects, provides applySnapshot and patches for cheap diffs and reconciliation, and exposes time-travel via recorded actions that replay or rebase changes. Demo builds a to‑do app with simulated server updates, uses TypeScript so TypeScript type checking and completion work on actions and models, and ties into snapshot listeners, localStorage persistence, and Redux DevTools-style inspection.
AI-written summary · about
chapters (8)
- 0:00Mutable and immutable state
- 3:09Plain objects and classes challenges
- 7:04MobX-state-tree benefits
- 16:26Snapshot-based state management
- 23:22Time travel and undo
- 26:53Server changes and patches
- 30:26MobX-state-tree and Redux DevTools
- 33:05Conclusion
related talks
48mMutable or Immutable? Let's do both!
34mImmer-mutable state management
21mNext-gen React state management with MobX State Tree
25mNext generation state management
32mMobX State Tree React pure reactivity served
41mmobx-state-tree, stop getting into all those states!
43mYou don’t know MobX State Tree
41mMobX, or: Going from Mutable to Immutable to Reactive State Management