[dead]
I don't think that you'd be able to get a very clear answer from your average frontend developer on why their non-React framework of choice uses the state management pattern that it does. For that matter, most DBA's wouldn't be able to answer detailed questions about their chosen database's query optimizer, and most ML researchers wouldn't be able to answer questions about Numpy's choice of linear algebra algorithms. Sometimes people just need to do their jobs without understanding every nuanced choice all the way down the stack. Luckily, software libraries let us do that.
I feel going out of one's way to use a 3rd party library like Redux with React is a bit different than a database's internal query optimizer.
Quite frankly the fact so many developers are replacing Redux with hooks is proof it was never the right choice for their project in the first place.
Or that Redux _was_ a reasonable choice at the time, and that with the ecosystem changing and other options available, it's worth re-evaluating use cases and updating the decision.
See https://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet... .
>Or that Redux _was_ a reasonable choice at the time,
Was it tho? The entire point of the post you linked is really about how "you might not need Redux" and for those who do, hooks can't replace it. If hooks can replace your usage of Redux than you never really needed Redux in the first place.
Personally, hooks have vastly simplified my code bases by giving me an out-of-the-box toolset for managing and fetching state. Not using redux means tons less boilerplate and actually means each "page" of my SPA's are totally decoupled from each other. (You can do this with redux by giving each page its own store but you need to be disciplined and refactoring can be tricky).