Front end developer specialising in JavaScript and React. Experienced in all aspects of modern front end development. Passionate about making accessible, secure and performant software.
Redux just moves your state management to a separate place. In other words it applies separation of concerns (single responsibility principle). As a result, your "view" code does less stuff and state management can be separately focused on.
When should you do this? When your React code gets too complicated to handle (because of heavy state management) and you feel it would be best to separate state management and move it elsewhere. Otherwise using React context is fine.
An additional consideration is that Redux and everything it requires (thunk, Sagas / redux-observables) are fairly complicated. This should be considered when deciding whether to introduce it or not.
EDIT: It's not deprecated. You just may not needed.
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.
Redux just moves your state management to a separate place. In other words it applies separation of concerns (single responsibility principle). As a result, your "view" code does less stuff and state management can be separately focused on.
When should you do this? When your React code gets too complicated to handle (because of heavy state management) and you feel it would be best to separate state management and move it elsewhere. Otherwise using React context is fine.
An additional consideration is that Redux and everything it requires (thunk, Sagas / redux-observables) are fairly complicated. This should be considered when deciding whether to introduce it or not.
EDIT: It's not deprecated. You just may not needed.