Try create and maintain an application of the size of facebook web for long time with context state and then come back here and rethink your comment hehe.
Redux is library based on state management architecture called Flow, all you team must respect strict design patterns.
If you want to replicate the behavior of redux with hooks, you must create a logical layer on top of the hooks and context API.
The state control in Redux is extremely strict and easy to debug and trace, you can only create actions and reducers that are pure functions, only in the middlewares flow can exist side effects.
dispatch-> action -> reduce-> return current state or new state
The downside to redux is that it is very verbose and this sucks, but currently does not exist another better alternative for large scale applications.
You can use redux-toolkit to create inmutable states and to make all things whit Redux more simple. Redux-toolkit
Try create and maintain an application of the size of facebook web for long time with context state and then come back here and rethink your comment hehe.
Redux is library based on state management architecture called Flow, all you team must respect strict design patterns.
If you want to replicate the behavior of redux with hooks, you must create a logical layer on top of the hooks and context API.
The state control in Redux is extremely strict and easy to debug and trace, you can only create actions and reducers that are pure functions, only in the middlewares flow can exist side effects.
dispatch-> action -> reduce-> return current state or new state
The downside to redux is that it is very verbose and this sucks, but currently does not exist another better alternative for large scale applications.
You can use redux-toolkit to create inmutable states and to make all things whit Redux more simple.
Redux-toolkit
Flux, not Flow ;)