Agreed on all counts. Like, I don't want _everyone_ to use Redux. I just want people to understand "here are the strengths, weaknesses, and use cases of tools

Agreed on all counts. Like, I don't want _everyone_ to use Redux. I just want people to understand "here are the strengths, weaknesses, and use cases of tools X, Y, and Z, and when it may make sense to use them". Honestly, we Redux maintainers (Dan, myself, Lenz Weber) have had to spend far more time telling people when _not_ to use Redux than we have trying to advertise the library :) When I rewrote the Redux docs tutorials last year, I made it a point to put "When should I use Redux?" right up front on the first page: 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... but that sadly can't have any effect on the thousands of existing tutorial pages or low-effort posts that are out there already.