@Nartc1410 @Enea_Jahollari @tmjee Yes aware and no disagreement! Just seems to recall (but might be wrong) that the improved modularity at DI level might enable some other changes having a positive outcome for the bundle size as well. But ok... just speculations for now! 😅

@Enea_Jahollari @tmjee Indeed... but the "counter-app" example might rock at bundle size level! 😂

@Enea_Jahollari @tmjee I guess ng will gain modularity and likely better tree-shakability (no need for DI? Code not bundled).

@Jean__Meche @Armandotrue @renatoaraujoc @OmerGronich Just an idea... But I see as well the potential disruption coming from "CDS.OnPush when not specified"! Same code will work differently... On the other hand, I guess good OnPush apps should get a reward... 😅

@Jean__Meche @Armandotrue @renatoaraujoc @OmerGronich Of course: - optional migrations, - optional build flag saying "don't make the build failing: OnPush when omitted". Downside: decorators with more / same data.

@Enea_Jahollari 🥳

@Jean__Meche @jsguidev I see... so technically speaking, the order - Effect fires - computed - isEven: true is not guarantee. Meaning, it could be: - computed - Effect fires - isEven: true I consider it irrelevant... but still

@jsguidev @Jean__Meche Well, an effect fires always once while computed are lazy (and there's no computed in the template read by the "view effect"). So: the effect runs and the computed is read... Effect fires computed isEven: true

@Jean__Meche @OmerGronich Signal components = ❤️ 😂 Even if my top feature remains better content projection!

@Enea_Jahollari Then IMHO a bit of consistency with - afterRender, - afterNextRender, - afterRenderEffect, wouldn't hurt (and maybe some reworking on the names)! 😅

@Armandotrue Beloved javascript! 😂😂😂 But yeah... not pretty

@Armandotrue Say: any case is different, but I'm typically fine with clickMethod() { // ... clearTimeout(this.tRef); this.tRef = setTimeout(() => {...}, 300); } or any equivalent beautification! Sure there might be very complex scenarios that cannot be rephrased... but still

@Armandotrue Umh... like clicking a btn (or equivalent) 1M times without 1M side effects? Basically debouncing... That's what you have in mind?

@Enea_Jahollari imho outdated! 😂 Say: I often feel that great improvements to ng would simply come from deprecating / removing things. See: ngIf / … / ngClass / animations / …

RT @synalx: @DanielGlejzner To be honest, one of the biggest drivers of the "Angular Renaissance" has been a culture shift of the team over…