3 ms·
Redux is not that hard to learn so why not? Why spend more time debating whether to learn something than just learn it?
by tempsy 7y ago
Redux is not that hard to learn so why not?
Why spend more time debating whether to learn something than just learn it?
- Supermancho 7y agoIt's hard enough. I haven't needed it in developing/contributing to my own frameworks and there's an infinite amount of things to look into. Right from the Redux docs (https://redux.js.org/faq/general/#when-should-i-use-redux https://redux.js.org/faq/general/#when-should-i-use-redux) - the link https://gedd.ski/post/what-not-to-learn/ https://gedd.ski/post/what-not-to-learn/
- tempsy 7y agoDunno. Perhaps there’s more functionality than the core but all it is is a plain JavaScript object that you “update” that you can access from different parts of your app. It really isn’t that complicated.
- jkoudys 7y agoI'd argue that Redux is so downright trivial to learn, there's a good chance that you already know it. The part that takes a bit of study is learning flux. You should already know how a reducer function works from Arrays, and all that makes the Redux approach special is your accumulator is read-only. The implications and advantages of all this are huge and take some time to really appreciate, but you shouldn't lose much time being confused and unproductive. The flux concepts of one-way data flow, action creators, etc. are the bigger ideas that take some study.