Right there with you on this, love react's rendering model. Redux seems to get all the hype but I'm sort of beginning to suspect it might be mostly the wrong way to do things. It reminds me of TDD, most of the benefits seem to be moral in character rather than concrete.
I know it's not the main point but you're talking about Redux there, not React. I've worked with React for years without touching the stuff you're talking about.
My take away was that we need to work towards converging efforts rather than diverging and causing constant fragmentation and lost effort. It being easy to deploy is a good thing, but people need to try to reduce noise and fix existing good enough projects to make them great and robust.
Contrary to my above points, I'm super in redux and react and feel they were large leaps in design over previous ones. I've been happier and happier with react over the last two years. Redux is also consistently making me smile.
It seems like Redux + React is clearly going to win out. What am I missing?
Yes the ecosystem is constantly changing right now but the oscillations are getting smaller not bigger. In my opinion Redux is the highest level and most intuitive, just like React was for the view when it came out. It's only a matter of time.
In my experience the experience with Redux Toolkit is awesome, it's essentially an opinionated way to use Redux for modern web applications and I believe they really hit the mark when it comes to reducing boilerplate and the need for extra deps. Although I'm still not a big fan and prefer to use built-in tools of React to manage state when possible (now that we have Context, Suspense, etc.)
How often do you see redux used with anything other than react? Or are you just talking about redux working with react alternatives like preact/inferno, etc?
You're not wrong, but practically 99% of people pair it with react.
I was a relatively early adopter of Redux and, while I understand the appeal of the architecture and mental model, I was always annoyed by the boilerplate (to turn plain language functions into serializable events) and unclear approach to modularization (single state tree is too much like a global). For moderately complex apps I found the practical downsides of those heavier than the pros of unidirectional flow and reproducible execution. Haven't touched it in over a year so I can't say if things are better, but somehow I doubt it.
This is precisely why I've been pushing for Redux even outside of the React ecosystem. I've been talking to quite a few people interviewing for ng2 projects... regardless of my opinions on ng2, something like Redux is probably a good idea for most projects (beyond trivial complexity, to relatively large).
reply