Managing State Management
summary
Argues that UI state and server cache are different problems and separating them simplifies everything, using react query for server cache and plain React (useState/useReducer + lift state up then push it back down) for UI state; shows a counter example and a notifications provider moved into its screen to co-locate providers, which enables code splitting and easier maintenance; recommends composition before context to avoid prop drilling and suggests recoil only if real performance bottlenecks remain.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:11Server Cache Is Not the Same Thing as Ui State
- 9:11Example Component Tree
- 9:42Authentication
- 13:52Responding to Changes
- 16:35Prop Drilling Problem
- 21:24React Use Context Hook
- 22:50Co-Location of Your Providers
- 28:24Review
related talks
40mManaging Complex State in React
23mThe State of State Management in React
41mThe Battle of State Management in modern frontend applications
17mManaging React State: 10 Years of Lessons Learned
29mAvoiding the Biggest Mistakes in React State Management
27mPut it All in State
24mGoodbye, useState
52mState management in a GraphQL era