To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/DecodedFrontend. You’ll also get 20% off an annual premium subscription.
Yeah... I mean there are reasons for that because very often the wrong usage of rxjs or misunderstanding of how change detection works can drastically impact the runtime performance. However, I believe that zone-less apps + signals make angular more safe in this area ;)
XSS protection in Rederer2 seems another angular myth 😄 Actually, it doesn't do anything security-related. You can see the source code of it and see that it directly manipulates DOM - github.com/angular/angular/blob/14.1.2/packages/platform-browser/src/dom/dom_renderer.ts#L157
4:57 I think another big problem here is creating new array/object instances on every rendering cycle. Also if you pass the result as an input to another component, it keeps triggering ngOnChanges/input changes
We used a angular signals model feature in our project, and my colleague used its as a component input replacement, and turn out a poor performant code, its like child is updating its own model and other child are triggered on other childs update, can you please suggest a best way to use signal model as i am not sure why angular team created it. Thanks
Really interesting to see how Angular has improved over the years. For styling ng-content etc., we use the :host ::ng-deep selectors together, which limits the styling to children of the host component without affecting the rest of the page.
Even if its older, i think host binding and host listener decorator syntax is better. I can see directly above the property/method what binding/listener that is related to.
To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/DecodedFrontend.
You’ll also get 20% off an annual premium subscription.
Thank you for making everything clear. But still, the haters will gonna hate. Their problem...
Excellent content!
Great video, thanks!
Great video, thank you!
Amazing content, as always. Thank you so much, Dmytro!! I'll start changing some myths in my code haha
Thanks 🙌
Thanks for sharing
Thanks for another useful video, Dmytro) I believed in some myths too :(
Hey Gagik! Thanks for your comment :) Which exactly myths did you believe if it is not a secret? I am just curious
@@DecodedFrontend about bindle size, pipes and Renderer2
Real MythBuster! :D
Exactly 😅
Great video. Every topic very well explained.
you forgot chapter 7 in the description
Good catch! It has been fixed. Thank you :)
angular developers have always been afraid about perfomance
Yeah... I mean there are reasons for that because very often the wrong usage of rxjs or misunderstanding of how change detection works can drastically impact the runtime performance. However, I believe that zone-less apps + signals make angular more safe in this area ;)
@@DecodedFrontend year, moreover, i believe that signals+zone-less are the new era of angular
I thought Renderer2 provided xss protection over direct DOM modification? If it weren't needed, it'd be deprecated or already removed, surely?
XSS protection in Rederer2 seems another angular myth 😄 Actually, it doesn't do anything security-related. You can see the source code of it and see that it directly manipulates DOM - github.com/angular/angular/blob/14.1.2/packages/platform-browser/src/dom/dom_renderer.ts#L157
I was'nt supposed to watch any video today, but i can't resist this 😍
I hope it will worth it 😉
Yeahhh!!!!!! dmytro time!!!
🙌 When Dany's article time? 😅
Thanks ❤
Interesting
Дякую, Дмитре за відео, було приємно побачити вас в айті Бороди!
Awesome Angular content Dmytro 👌
As usual, very informative !
most myths come from people who don't know Angular or wrote bad Angular code, messed up build configs and had slow code or large bundles
4:57 I think another big problem here is creating new array/object instances on every rendering cycle. Also if you pass the result as an input to another component, it keeps triggering ngOnChanges/input changes
We used a angular signals model feature in our project, and my colleague used its as a component input replacement, and turn out a poor performant code, its like child is updating its own model and other child are triggered on other childs update, can you please suggest a best way to use signal model as i am not sure why angular team created it. Thanks
Really interesting to see how Angular has improved over the years. For styling ng-content etc., we use the :host ::ng-deep selectors together, which limits the styling to children of the host component without affecting the rest of the page.
Maybe it's just me, but I still see a difference even on a clean generated project - the runtime in Angular is slower than in Vue and React.
Even if its older, i think host binding and host listener decorator syntax is better. I can see directly above the property/method what binding/listener that is related to.
Indeed a good video. Would be nice to see separate video on Myth 3
Feeling relaxed to know i am in right stack ☺
Great channel, and the angular course is also great!
First
🎉
doing the lord's work
Sadly second:(
Next time you will win ;)
Sorry. :D
still React is a 1.000.000x better
As per my suggestion don't go over angular it's most worst client side framework compared than other
Nobody asked, everyone needed. Thank you! 🦾