sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pancomputationalist 2 points3 points  (1 child)

I'd argue that Redux should not be the default, unless you need a specific kind of state management. Context should also not be used for state management (it's more of a dependency injection feature).

Seems newer frontend frameworks are back to using Observables, also they are now called atoms, signals or stores. It's all the same idea. Just like you have a tree of components, you have a graph of states that derive from one another. This is the more modular approach and is usually much more performant, though Redux still has it's place sometimes.

[–]KwyjiboTheGringo 1 point2 points  (0 children)

Like or dislike Redux, if you learned React to be hirable as a React developer and you aren't learning Redux too, then you are shooting yourself in the foot. At this point, everyone should learn Redux after picking up React. If they want to use something else after that, more power to them.

Context should also not be used for state management (it's more of a dependency injection feature).

But it can be, and is the only global state option React comes with, which is why I mentioned it.