Update FAQ: When should I learn Redux?

[maxhallinan]

This adds a "When should I learn Redux?" section to the General FAQ. The answer includes links suggested in #1785 . cc: @markerikson

[timdorr]

I feel like this should be combined with the "When should I use Redux?" question. They are quite related in my mind.

[maxhallinan]

I made the same comment on 1785. While I'm not confidant that I covered everything Mark intended for "When should I learn Redux?", it seems like there are two related but distinct ideas:

• The best time to learn Redux is when you have a problem that Redux solves. ("When should I learn Redux?").
• The problems that Redux solves are... ("When should I use Redux?")

Keeping the question about learning separate creates a space for the broader point about avoiding "JavaScript fatigue". But that question gives rise to and flows directly into the question of good use cases. So maybe placing "When should I learn Redux?" before "When should I use Redux?" helps to keep the answers simple and the flow coherent.

[markerikson]

Yeah, I agree that they're two separate questions. It's entirely possible to know Redux, but not be sure when you actually ought to use it.

[markerikson]

Hah! I love that this got added just a day or two after I tweeted it :)

[maxhallinan]

😀

[markerikson]

Pretty good start. Got a couple ideas for rephrasing things.

First, let me quote my "standard advice for learning React":

On that note, definitely don't over-complicate the learning process by trying to learn many different things at once. Some people will say you should use a "boilerplate" to learn React, and they're wrong - boilerplate projects almost always come with too many pieces configured, and are confusing for beginners.

Instead, the best 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, and you can learn about other tools later.

I'd like to see if we can use some of that phrasing. It's not so much that React is a "data-driven UI library", but that React already has a built-in pattern for managing state.

I definitely like that last sentence on "becoming so complex you're confused".

Another aspect I'd like to get into this is that we advise learning React first just so there's fewer concepts to understand at once. It's certainly possible for people to tackle them both at the same time, but for most people it's easier to focus on React first, then Redux after that.

[maxhallinan]

I've revised this to be more explicit that a UI library is possibly sufficient when the library includes a state management system. And I've added emphasis that beginners are best off starting without Redux. I'm reluctant to comment on React more specifically because it undermines the important point that Redux is not coupled to React. Saying "focus on React first, then Redux after that" could imply a preference for React more fundamentally. So I tried to incorporate the principles of what you're saying with less emphasis on React.

[markerikson]

A couple more very relevant quotes from the last few days to add. I suppose these could easily go under "When should I use Redux?" too.

• https://twitter.com/raquelxmoss/status/901576285020856320
• https://twitter.com/garetmckinley/status/901500556568645634

[maxhallinan]

I've added these links.

[markerikson]

I can also see a valid point to putting "When should I learn?" in front of "When should I use?". I'm not 100% sure I want to do it, but it's worth trying it out to see how it looks.

[maxhallinan]

@markerikson thanks for the review! I've updated this branch with a second draft that (I hope) addresses your feedback. I also moved "When should I learn..." before "When should I use..." and removed language about learning from "When should I use...". Let me know what you think.

[markerikson]

I'd say this looks good enough for now. Stamped!