4 ms·
Thank god it doesn't contain Redux, entirely optional and entirely complex. Just recently someone was telling me about how hard ReactJs was to learn and from w
by forgottenacc57 10y ago
Thank god it doesn't contain Redux, entirely optional and entirely complex.
Just recently someone was telling me about how hard ReactJs was to learn and from what I could glean, at least part of the learning challenge was because he felt he had to use Redux because many people perceive react and redux to go hand in hand.
- gillchristian 10y agoThat has to do with people used to frameworks and coming to React expecting that. I personally had the same issue. If you are used to framework based development (Angular, Vue, Backbone, etc) you are not used to making decisions for yourself and to chose when to use what. Don't get me wrong, opinionated frameworks are good and fill a gap. But you have to know that when you are developing using libraries you make those decisions yourself and thus you have to think a bit more when you chose something and why. Redux is just one way to handle state in React apps. Might be the most used one but by any means it is the only one or the silver bullet.
- acemarke 10y agoI'll point out that both the React team (particularly Dan Abramov) and the Redux team (especially myself) discourage people from trying to jump into both of those together at once. In fact, my copy-paste answer is: > The standard advice is to focus on learning React itself first. Once you have a good understanding of how React works, you will better appreciate why a state management library like Redux can be useful. Don't over-complicate the learning process by trying to learn many different things at once. But yes, it does seem like large portions of the community insist that you _must_ use Redux with React, you _must_ use Redux right away, and even that you _must_ put _everything_ into Redux. None of which are true :)