TL;DNR: Context is a means by which an external state management capability can be acquired (e.g. get a hold of Redux to subscribe to the store; the "value" in Context used to subscribe to the store never changes while the application is running). Context itself is not for state management.
...context is ready to be used for low frequency unlikely updates (like locale/theme)... It's not ready to be used as a replacement for all Flux-like state propagation.
Mark Erikson
@acemarke
@Meligy@dan_abramov@hersman@ryanflorence@reactjs That said, I've noted that React devs can often be classified into two groups: those who see the React tree as their app / have a "component-centric" view, and those who view their state / logic as their app / have an "app-centric" view.
Many Redux users are in the second group.
22:10 PM - 28 Oct 2018
If you decide to look into Redux, Mark Erikson recommends to start with Redux Toolkit.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
TL;DNR: Context is a means by which an external state management capability can be acquired (e.g. get a hold of Redux to subscribe to the store; the "value" in Context used to subscribe to the store never changes while the application is running). Context itself is not for state management.
Why React Context is Not a "State Management" Tool (and Why It Doesn't Replace Redux)
Quote:
If you decide to look into Redux, Mark Erikson recommends to start with Redux Toolkit.