DEV Community

Minko Gechev on Angular 16 & 17 — game changer or loss of identity ?

Daniel Glejzner on April 18, 2023

In a recent podcast, Minko Gechev — Lead and manager for Angular developer relations - shared valuable insights into the future of Angular and it...

Read full post

Comment deleted

Tomas Rimkus • Apr 21 '23

"OnDestroy" is usefull for those who are using RxJS in imperative way. See "ngneat/until-destroy" library for more info.
In most cases Signals is a much better solution than plain RxJS in Angular. It's easy to learn, integrates well with Angular, performant out-of-the-box without any need for stupid RxJS hacks ("debounceTime(0)", "shareReplay()", "distinctUntilChanged()", etc), can be converted to RxJS Observable if you want to use RxJS operators.
Standalone Components is extremely nice feature, because it reduces boilerplate code, allows you to have a nicely structured tree of dependencies (unlike the "NgModules" way where people just throw everything in their bloated modules (especially "SharedModule")), allows you to clearly see what component depends on other components, allows you to have "standalone" directives and pipes without modules. In general, "NgModule" became a bloated mess over the years with 9 configs, out of which only 4 are actually used in most apps. You can also lazy load standalone components by using "loadComponent" or "loadChildren" Route configs.

Marcin • Apr 20 '23

OnDestroy ref could be very useful to get rid of unsubscribe event emitters/subjects.
While there is a package called until destroy it will become pointless when angular will have it's own observable point of reference to know when a Component is destroyed. Simply - Less boilerplate

Signals are far easier to learn/understand/use and will be quicker to implement than let's say BehaviorSubject. At least that seems to be the idea.

For me standalone components are a lifesaver when it comes to largely reusable components. Something that would otherwise have to be stuck inside a shared module can now be it's own thing without the need to create a module.
And then there is the SCAM pattern that is pretty much replaced by standalone components.