Nice article! I’ve used both redux and ngrx extensively and must say that while I appreciate the effort of the ngrx team it feels so unintuitive compared to the pure redux implementation.
A colleague once told me to only use redux for state that needs to be accessible elsewhere or fetches data and keep all the rest as local state. While not necessary I really like how this simplifies debugging and keeps the reducers from growing out of control.
That's a good tip, though it does get rid of some of the centralized aspects.
There are some lighter weight Angular state management libraries out there that may be more of a happy medium as well, but I've not looked into them yet.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.