Redux
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
Why people recommend it
“Well structured redux (or mobx or zustand for that matter) can be highly maintainable & performant”
“Even now I am not sure I could find a better tool to deal with real time data and synchronization.”
Caveats and dissent
“it required writing a lot of code across multiple files even for incrementing a number”
Show 2 more
“Redux should not be used for 1 person projects.”
“Redux which has a very unintuitive API”
Often compared with
Who recommends it in their own words
From the makers not counted in the ranking
“have recommended a more integrated-style approach to testing for a while”
“Redux is still by far the most widely-used state management library in React apps.”
“there's perfectly understandable reasons why we ended up there”
Threads where it came up
- RCE Vulnerability in React and Next.js 3 mentions
- jQuery 4.0.0 Released 2 mentions
- You can't design software you don't work on 2 mentions
- Ask HN: Who wants to be hired? (October 2026) 1 mention
- Htmx 4.0 1 mention
- Ask HN: Who wants to be hired? (August 2026) 1 mention
Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 23
“Redux”
“No Redux or Next.JS”
“Redux, MobX, Logux”
“don't use Redux until you have problems with vanilla React.”
“Technologies: React.js,Vue.js, Next.js,Nuxt.js ,TypeScript, SCSS, CSS3, Tailwind CSS, Redux, Zustand”
“it required writing a lot of code across multiple files even for incrementing a number”
“Redux”
“if you’ve worked with state management like Redux, I would argue that hooks are pretty similar”
I'm sympathetic to "it's the browser's fault", to some degree. I understand that the browser locks you into certain constraints, and I understand that I don't understand much about those constraints, because most of the extent of my experience with web development is using a canvas and a couple of fundamental APIs to render my games via WASM as web is one of my build targets (and I do know that approach is undesirabl
“Redux”
“Redux should not be used for 1 person projects.”
“Redux which has a very unintuitive API”
“Tailwind, Redux, react-query”
“Well structured redux (or mobx or zustand for that matter) can be highly maintainable & performant”
“Irrelevant updates happen all the time with this stack.”
“Even now I am not sure I could find a better tool to deal with real time data and synchronization.”
It's essentially the same problem as https://xkcd.com/927/ [How Standards Proliferate]
“the random 10k lines written in Redux (not used anywhere else) that no one likes working with”
“I wouldn't have used redux if I was!”
“my boss is pushing "redux everything" as the next step”
“That avoids the opaqueness of Redux and promise chains”
“"Immortal State" (Zustand/Redux, where state stays in memory forever unless manually reset)”
“if, say, you're using something like Redux or ngrx where immutability is a design goal and so you're cloning your application's runtime state object”