The State of React and the Community in 2025

blog.isquaredsoftware.com

2 points·rk06··3 comments

I think the reason why React has shown so much staying power is that as apps get larger, they don't necessarily get more complex from a management perspective. Components, for the most part, are very self contained and with modern toolchain, you can easily see dependencies and refactor components.

This is a very different world view from $() and {{}} from earlier concepts where you hook onto globally named things. In React (without redux) you can nest and make independent memory mapped components. Redux was a terrible start in the React world, but thankfully hooks have eradicated it from most people's memory.

It's ironic you say that - I wrote the post, and I _maintain_ Redux :)

FWIW, I can confirm that hooks have _not_ "eradicated Redux" - it's still the most widely used client side state management lib in React apps. It's definitely as common as it used to be, since the ecosystem has evolved significantly, but both download stats and discussions with devs tell me it's still in very widespread use.

We can have different opinions, but every project that had Redux in the wild that I ran into had side effects and unexpected behavior everywhere. With hooks (state and context) it completely removes the need for Redux anywhere and most libraries are best kept clean without requiring anyone to use Redux.

To me Redux is like arguing to use C with global variables. Hooks (usestate/usecontext mostly) are local variables and it makes much more sense.

Reply on news.ycombinator.com