I've never understood why redux gets implemented so badly... I feel that the folks who build wacky redux implementations would still write spaghetti managing state without redux.
That's why we published our official Redux Toolkit package in 2019. It standardizes Redux usage, and includes methods that build in our recommended approaches for things like store setup, writing reducers, simpler immutable updates with Immer, and even a complete server data fetching and caching solution called RTK Query:
- https://redux.js.org/introduction/why-rtk-is-redux-today
- https://redux.js.org/tutorials/essentials/part-2-app-structu...
We routinely get highly positive feedback from folks who hated writing old-style Redux, but love using RTK.
Related, we also have a "Style Guide" docs page that provides guidance on what approaches we recommend using when writing Redux code:
Obviously, deleting Redux from the internet to prevent incompetent engineering leads / managers from forcing it on people would be preferable.
They're not even substitutes; RTK Query by default wraps fetch or can be configured to use your preferred http client. So it's an entirely additional layer of cacheing and refetching logic with a standardized interface around common loading and error states.
It is considerably easier to write performant web applications with a library like RTK Query or TanStack Query than to just use fetch and try to roll your own cacheing solution. I say this as someone who has done all of the above professionally.
It is a completely different skillset and I think more often than not people assume that they can write front end code just because they know Javascript.