Unpopular Opinions
summary
Argues that the useful claim is not that context or hooks exist but that stuffing all entities into one store context causes full re-renders so a chat app with even a few hundred friends and 200,000 users in production shows lag and wasted work. Shows concrete fixes: split contexts, selectors or caches (Relay/Apollo/Redux with reselect), avoid duplicate state breaks consistency, and recommends judging tech in the context of time and thinking two steps ahead before swapping state management.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:42Why Redux
- 5:17Whats Next
- 7:55More Works
- 8:35State Management
- 15:54Context
- 17:04Rerendering
- 18:08Contexts
- 19:13Feature Requests
- 20:37Duplicate State
- 21:36React Memos
- 23:02Separate Caches
- 24:08Current User
- 24:37Think Twice
- 25:25Alternative
- 26:28Summary
related talks
19mMy unpopular ReactJS opinions
35mNavigating the Hype Driven Frontend Development World
29mAvoiding the Biggest Mistakes in React State Management
30mManaging State Management
35mHandling Large-Scale State Management with Context and Hooks
30mMake React State-Management great again
29mStructure Your App's Story With Sagas and Selectors
47mEmbrace the "react fatigue"