NGRX in Angular 7

[Tim Consolazio]

If you've been resisting it, or really don't understand how to use it in more than a basic sense, it's time to shore up your NGRX skills. Angular 7 integrates it as a first class citizen. 

I'm not sure how I feel about that. When Angular integrates something, the expectation is, "that's how you'll do it from now on." NGRX has changed a lot (e.g. there's no more store.value, which might be a good thing, but still...) not to mention when you couple it with the ever-changing complexity of RXJS (do we use compat? Do we import pipe-able vs. "regular", can the two versions coexist...?) you can really get into some deep head scratching. 

Myself, I think NGRX is over engineered. I've made a point of understanding it, and I use it in a very large project every day, in fact I drove the organization I'm working with to standardize on it for module data sharing and as an event bus (something we used to do in three lines of code with a Subject...argh...). I see the value of the approach. But the implementation just seems so verbose, and I've read a lot of things online that would seem to assert the same. 

That all leads me to believe that Angular 7+ projects are going to experience a lot of changes that will compromise a lot of "not so old" code; historically this has (frustratingly) been the case (e.g. deprecation of http modules and component factories, which of course are in heavy use everywhere).  But, in the Angular world, god forbid you implement your own thing; the Angular Chorus will shout you down. 

What do you think?

[trust...@gmail.com]

I dont know much about ngrx except for it has something to do with observables.