Panel discussion about state management
summary
Panelists argue that the practical decisions matter: a prototype for visual-first code generation exists and aims to emit code from diagrams; Overmind emphasizes typing ergonomics; experiments show state machines/statecharts tame behavior drift better than ad hoc object mutation; Context API works for theming but breaks at scale; GraphQL helps fetching but complicates local updates; Comlink-style web worker stores and web workers for heavy state or wasm help large datasets though they introduce latency and debugging costs.
AI-written summary · about
chapters (10)
- 0:00Panel introduction
- 0:23State management future
- 4:57Context API at scale
- 7:49React Suspense features
- 9:32GraphQL in state management
- 14:33Past state management ideas
- 15:15Web workers for state
- 19:55WebAssembly performance
- 20:58React performance challenges
- 23:28Closing remarks
related talks
52mState management beyond the libraries
41mThe Battle of State Management in modern frontend applications
33mPanel Discussion – State Management
24mPanel discussion hosted by the Apollo team on GraphQL + React
57mThe State of State
27mAMA with Michel Weststrate
28mThe two ways to manage state
37mReactive State Machines and Statecharts