The Mutable State Monster and How to Defeat It
summary
Explains how mutable shared state causes race conditions and nondeterministic bugs that complicate reasoning and debugging, and proposes referential transparency and immutable data structures as concrete solutions. Demonstrates these techniques with an Android example, includes microbenchmarks of latency and memory overhead, and reports a real component refactor that compiles, runs, preserves performance, and simplifies debugging.
AI-written summary · about
chapters (5)
- 0:00Mutable state challenges
- 12:03Mutable state problems
- 22:04Uncontrolled mutable state
- 33:18Managing mutable state
- 40:09Summary
related talks
32mThere and Back Again: Grokking State and Data
52mState management beyond the libraries
32mThe State of Representing State
01h 03mRefactoring to Immutability
19mThe Art of Functional State Management for iOS Apps
28mThe Art of Functional State Management
43mState Manager Architecture
45mExploring the possibilities of Unidirectional Data Flow Architectures on Android (en)