This is an excellent read - thanks for posting this. I have seen multiple times developers reaching out for Redux almost automatically for their projects. It seems to be the go-to tool for state management, even though in reality Redux was designed to solve a very specific, global state management problem - which an app might not have. By the time the app has reached a certain size, it is very hard for teams to imagine a cleaner approach exists. I think part of the problem is with the resources available for newcomers to React, where tools like Redux are mentioned in every tutorial. Its important to understand the problem the tool is designed to solve, before using it.
I would be interested to know what kind of feedback you got from teams using Redux when you brought up the idea it isn't always necessary.
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.
This is an excellent read - thanks for posting this. I have seen multiple times developers reaching out for Redux almost automatically for their projects. It seems to be the go-to tool for state management, even though in reality Redux was designed to solve a very specific, global state management problem - which an app might not have. By the time the app has reached a certain size, it is very hard for teams to imagine a cleaner approach exists. I think part of the problem is with the resources available for newcomers to React, where tools like Redux are mentioned in every tutorial. Its important to understand the problem the tool is designed to solve, before using it.
I would be interested to know what kind of feedback you got from teams using Redux when you brought up the idea it isn't always necessary.