The State of React State Management
summary
Survey of options claims React has no official state layer and that Context has a fatal re-render flaw (any change forces consumers to re-render). Redux is battle‑tested but is essentially one big object in the sky with lots of boilerplate; Redux Toolkit and hooks reduce that pain. MobX is reactive and lighter but less conventional. Modern choices split into atomic atoms (Recoil, Valtio, Jotai, Zustand—Valtio favored here) and query caches (React Query, SWR preferred over Apollo). Practical advice: pick the tool designed for each job.
AI-written summary · about
chapters (15)
- 0:00Introduction and overview
- 2:49React state management basics
- 5:15Why React lacks built-in state
- 10:11Redux and its evolution
- 14:43Opinions on Redux today
- 15:04MobX and reactive programming
- 17:30Community feedback on MobX
- 18:11React Context limitations
- 21:40Hooks impact on state
- 23:46Atomic state management libraries
- 26:56Query cache libraries explained
- 30:26Future of React Context
- 31:51State management fragmentation
- 33:15Final thoughts and summary
- 33:58Q&A session begins
related talks
55mThe State of React’s State in 2019
28mThe State of React State in 2019
40mReact State – The Good, the Bad and the Ugly
42mReact in All Its States
36mModern React and the case for Reactive State Management
41mThe Battle of State Management in modern frontend applications
23mThe State of State Management in React
18mDestructuring state management (in React)