Context is how state (that exists somewhere already) is shared with other components.
Context has little to do with state *management*.
01:56 AM - 09 Jan 2021
Phrased differently: Context is a place for "first introductions" between components and cross-component state (management) but not for "regular meetings" between them.
In my opinion the countless "don't need Redux, just use Context" statements communicate a misunderstanding of what context actually is.
There are "lighter" (cross-component) state management solutions like unistore, valtio, zustand and jotai.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am Sorry, I should have mentioned about the things me might store in Context (like which changes not on regular basis) and the things we might not.
No need to apologize — for the most part the official docs are silent on the matter and I only became aware of it through Mark Erikson's Why React Context is Not a "State Management" Tool.
Phrased differently: Context is a place for "first introductions" between components and cross-component state (management) but not for "regular meetings" between them.
In my opinion the countless "don't need Redux, just use Context" statements communicate a misunderstanding of what context actually is.
There are "lighter" (cross-component) state management solutions like unistore, valtio, zustand and jotai.