React State – The Good, the Bad and the Ugly
summary
Compares concrete state solutions: component state and Hooks for local UI state, Redux = one immutable store + lots of boilerplate and middleware for side effects, Flux as older mutable-multiple-store pattern, Relay solves client‑server sync out of the box for GraphQL, and MobX uses observables/reactive streams with less boilerplate but harder debugging. Argues choose by project size and team knowledge, warns against overengineering (example: a simple blog built with GraphQL Relay AWS Lambdas etc.), and recommends learning basic React state before adding libraries.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 2:40The Bad
- 4:20Comparing to Modern Web Applications
- 5:18What is State
- 10:10History
- 11:47Component State
- 12:48Pros and Cons
- 14:31Flux
- 16:27Pros of Flux
- 20:05Redux Pros
- 21:10Redux Cons
- 22:30GraphQL
- 24:04Relay
- 27:43The Pros
- 28:52The Cons
- 29:34Reactive Programming
- 31:25Pros
- 32:45Cons
- 33:57Context API
- 36:20React Hook
- 37:07Conclusion
related talks
28mThe State of React State in 2019
47mThe State of React State Management
55mThe State of React’s State in 2019
36mModern React and the case for Reactive State Management
30mReact state management in a GraphQL era
24mReact State Management In a GraphQL Era
15mRedux is dead, long live redux!
30mMake React State-Management great again