Good question! The really short answer is: mostly looking at NPM download stats, Github "depended by" numbers, and random polls on Twitter. Which are all _hor

Good question! The really short answer is: mostly looking at NPM download stats, Github "depended by" numbers, and random polls on Twitter. Which are all _horribly_ flawed metrics, but they're also all we have to go by. I wrote a couple longer comments on Reddit a while back that went into more details on some of the numbers and the potential flaws in using them: - https://www.reddit.com/r/reactjs/comments/lcgqnd/state_management/glzrax4/ https://www.reddit.com/r/reactjs/comments/lcgqnd/state_manag... - https://www.reddit.com/r/reactjs/comments/skbyb1/the_most_popular_react_tech_stack_in_professional/hvlwdpw/?context=3 https://www.reddit.com/r/reactjs/comments/skbyb1/the_most_po... and unfortunately you asking me about this is tempting me to turn those comments into a blog post with some additional thoughts :) (I.... may actually try to do that tonight or tomorrow. If you're interested, keep an eye on my blog at https://blog.isquaredsoftware.com https://blog.isquaredsoftware.com .) I'll definitely agree that Redux usage has peaked in _relative_ terms, although as you can see from the download numbers it seems to still be growing in _absolute_ terms. Also it's entirely possible that fewer new projects are choosing Redux. Then again, how do we even count "usage" in the first place? I've seen Web3 app boilerplate repos that include Redux Toolkit. If 1000 people clone that repo and play with it, how do we compare that usage conceptually vs one app using Mobx that's been around for years and has a bunch of developers working on it daily? As I've pointed out in a number of podcasts and articles: I'm not trying to convince people they _must_ use Redux, or even that they _should_ use Redux. I just want people to be aware that modern Redux is way easier than legacy Redux, that Redux _is_ still widely used and is a viable choice, and what some of the tradeoffs are when using Redux or any other state management library. I've actually been trying to get the community to come together and work on a centralized site that would list tools in different use cases and categories such as state management, styling, data fetching, and build tooling, describe purpose / use cases / tradeoffs for each tool, and have that as a recognized resource for people to use when researching what to use for a project. You can see the original RFC discussion and prototype site here: - https://github.com/markerikson/react-community-tools-practices-cheatsheet/discussions/1 https://github.com/markerikson/react-community-tools-practic... - https://react-community-tools-practices-cheatsheet.netlify.app/state-management/overview https://react-community-tools-practices-cheatsheet.netlify.a... Sadly I haven't had time to push this forward, and it needs to have more people involved and helping fill out content on the various topics (not just me).