2 ms·
I've seen many developer hours go into meetings to decide if we should use Redux, and individual developers sent off on investigatory missions to see if they co
by phendrenad2 6y ago
I've seen many developer hours go into meetings to decide if we should use Redux, and individual developers sent off on investigatory missions to see if they could shoehorn an existing React app's state into Redux. It feels like everyone thinks they "should" be using Redux, but in practice it takes time to do the refactor, and time isn't free.
- acemarke 6y agoFWIW, I'm a Redux maintainer, and our docs explicitly offer some rules of thumb for when it might make sense to use Redux: https://redux.js.org/faq/general#when-should-i-use-redux https://redux.js.org/faq/general#when-should-i-use-redux https://redux.js.org/tutorials/essentials/part-1-overview-concepts#when-should-i-use-redux https://redux.js.org/tutorials/essentials/part-1-overview-co... https://redux.js.org/tutorials/essentials/part-2-app-structure#component-state-and-forms https://redux.js.org/tutorials/essentials/part-2-app-structu...
- quickthrower2 6y agoThanks. I am asking a slightly different question, and I probably didn't make it clear enough, but I am asking if you should LEARN Redux. Not whether to use it on project X. Often in this fast moving world, it is worth learning some concepts so that you know when they would be useful, and because of job interviews and such like. I'll update the article when I get a chance to include acemarke's advice on when to USE Redux though.