Increase visibility of when to use Redux vs when not to use Redux in docs

[dyst5422]

The docs currently has a section on the first page Before Proceding Further which has a single link to a Medium article Dan wrote a year and a half back.

This effectively hides when NOT to use Redux behind a link and article post. I know dissuading people from using the library isn't a great way to do PR, but I think there are a LOT of people that get into using Redux for the wrong reasons or jump in too soon. The amount of overhead Redux requires leaves a sour taste in their mouth.

I propose a simple 3 big bullets when to use Redux and 3 big bullets of when NOT to use Redux, as well as perhaps suggestions for other tools that may fill certain use cases better.

[dyst5422]

As I was writing this, I thought of the use case of a client side data-cacheing layer where Data Loader or Apollo Client (if you're using GraphQL) would be a better option in the alternative tools section.

[markerikson]

Yeah, Dan has honestly spent more time telling people to not use Redux than he has promoting it :) And yes, there are some valid reasons why he's had to adopt that sort of approach.

I'd be very happy to take a PR that updates that section. I'd suggest looking at the FAQ entries for When should I use Redux? and Can I split state between Redux and React component state?, and summarize the points in those answers.

Also, my two posts on The Tao of Redux, Part 1 - Implementation and Intent and The Tao of Redux, Part 2 - Practice and Philosophy may be worth linking alongside "You Might Not Need Redux", since they provide context and background for why Redux is built the way it is and how it's intended to be used.

[markerikson]

Closed by #2851 .