I appreciate the article, but we really need to be cautious about writing "depends on the size of the project or situation" type articles related to Javascript development choices.
In particular, with React, Redux has been a major source of project delays and near failures in my 4 years of React dev experience. Also, arguing over "redux vs mobix vs context" has created thrashing on projects, division in the community and another wave of "javascript fatigue".
Use Redux for legacy applications only! Use Context going forward. ...And spend time focusing on your product, not hemming and hawing over esoteric concerns.
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 appreciate the article, but we really need to be cautious about writing "depends on the size of the project or situation" type articles related to Javascript development choices.
In particular, with React, Redux has been a major source of project delays and near failures in my 4 years of React dev experience. Also, arguing over "redux vs mobix vs context" has created thrashing on projects, division in the community and another wave of "javascript fatigue".
Use Redux for legacy applications only! Use Context going forward. ...And spend time focusing on your product, not hemming and hawing over esoteric concerns.