I'm not totally convinced this makes things better. To me, the problem with Redux is the whole act of having a ritual ceremony around every mutation you want to make to your state. To put things in perspective, I'm currently building an IDE from scratch "game development" style, in that I have a global "world" state that gets reflected in the rendered UI 144 times a second. So it's a similar paradigm to React -- except when I want to modify state, I just do it. Like I literally just mutate the variable by writing to it. Sometimes I do a particular mutation in many places and at that time I will pull it out into a function, but in general writing to state is not this enshrined procedure. I could not fathom developing this thing while having to create a new slice/duck for every state change I want to make.

I guess some people see the enshrined procedure as a feature and not a bug, and it is possible you could weigh the benefits of Redux's features against the cost in engineering time and decide it's worth it.. but it doesn't seem like this tradeoff is being consciously made and analyzed. It seems more like everyone just assumes they need something like Redux the moment they have global state.