This is the beginning of a new playlist focusing on the future of Angular. 😊 But don't worry, I'm not done with the Angular Mistakes series yet 😉For a full course on Angular, including the Signals API, check out my Angular Core Deep Dive course - angular-university.io/course/angular-course
No worries, I will leave it on in the intro only, and lower it in future videos, this was just an experiment. It wont be as load next time, thank you for the feedback 👍
Hi Vasco, amazing stuff! And not only signals, but your content as well! I watch a lot about angular, and work full time using it, and currently there is no better angular videos on YT 🔥
Great overview. Additional comment: change detection is not limited to component level - it's even down to fragment level ( so, a DIV for example). This is a potentially huge gain , depending on your component of course. Cheers
Thank you Lars, indeed with signals the granularity will be the template view, for example a block inside a @if block. I am thinking of covering this in an upcoming video. 😉
There were so many times when I tried to use signals, but I always realized that I need the power of RxJs operators, so I just ended up using observables.
Sure, that also works. You can also combine them: signals for managing state, async/await for every day HTTP and asynchronous code, RxJs for advanced cases. Signals as great RxJs integration like toSignal() etc.😊
Hi Vasco, great Videos! I have a question. At 3:08 you state that you can inject the service using the inject function. Isn´t it possible to use "normal" dependency injection through the constructor?
Yes, we might be coming full circle 😊 But notice that in principle there won't be a proxy-based solution at the level of the framework, there is no indication of it. Maybe as a library, who knows. 👍
Nāo quiz inclui-los neste video, para nāo ficar demasiado longo, mas cobri essa funcionalidade neste video 😊 - ruclips.net/video/abUBuWVwK14/видео.html
@@AngularUniversityYes, that was my point, you have look into the effect to see which signals it applies to, it's not immediately clear just looking at the start of the effect.
This is the beginning of a new playlist focusing on the future of Angular. 😊 But don't worry, I'm not done with the Angular Mistakes series yet 😉For a full course on Angular, including the Signals API, check out my Angular Core Deep Dive course - angular-university.io/course/angular-course
Thank you Vasco! Would be nice if we have an option to lower the background music volume (possible?) or completely do without it.
No worries, I will leave it on in the intro only, and lower it in future videos, this was just an experiment. It wont be as load next time, thank you for the feedback 👍
Hi Vasco, amazing stuff! And not only signals, but your content as well!
I watch a lot about angular, and work full time using it, and currently there is no better angular videos on YT 🔥
I really appreciate your kind words. Stay tuned for more videos and Shorts!
Great overview. Additional comment: change detection is not limited to component level - it's even down to fragment level ( so, a DIV for example). This is a potentially huge gain , depending on your component of course. Cheers
Thank you Lars, indeed with signals the granularity will be the template view, for example a block inside a @if block. I am thinking of covering this in an upcoming video. 😉
Your talks about change detection and state management was very useful. Thanks!
Hello Sinan, thank you I'm very happy to hear that 😊
There were so many times when I tried to use signals, but I always realized that I need the power of RxJs operators, so I just ended up using observables.
Sure, that also works. You can also combine them: signals for managing state, async/await for every day HTTP and asynchronous code, RxJs for advanced cases. Signals as great RxJs integration like toSignal() etc.😊
Guessing b/c of the number of changes you could have a course of how to write angular app today and improve it as the new updates come along.
Yes, I'm adding new sections and lessons to the Angular Core Deep Dive course. 😊👍
Great as always. Thanks a lot!
Thanks, I really appreciate that you like my videos!
👍😀 Very dynamic class
Thank you, please enjoy 😊
Hey, your IDE looks so good!! Whats it's name? Do u have some custom theme or font?
This is the Webstorm IDE, with the Monokai Pro theme (it's free) 😊
Hi Vasco, great Videos! I have a question. At 3:08 you state that you can inject the service using the inject function. Isn´t it possible to use "normal" dependency injection through the constructor?
Thank you, yes that also still works, I just have been using more the inject function lately, but both ways work.
Loving Angular signals but I can't help but see knockout.js and backbone.js similarities 😂 I guess what goes around comes around 😂
Yes, we might be coming full circle 😊 But notice that in principle there won't be a proxy-based solution at the level of the framework, there is no indication of it. Maybe as a library, who knows. 👍
Thank you. But we don’t need a background music when we are trying to learn. ❤
Noted! I will reduce it significantly on upcoming videos, it was just an experiment. 👍
Esqueceste os model Inputs e os query signals
Nāo quiz inclui-los neste video, para nāo ficar demasiado longo, mas cobri essa funcionalidade neste video 😊 - ruclips.net/video/abUBuWVwK14/видео.html
😊
One comment about the effect the scope of the effect is not clear without looking at the implementation.
The effect gets triggered whenever any of the signals used inside it emits a new value.
@@AngularUniversityYes, that was my point, you have look into the effect to see which signals it applies to, it's not immediately clear just looking at the start of the effect.
signals are literally dead on arrive
can you share why you think that? It seems to me that it's going to become the de facto way of building applications in Angular. 👍
Angular has hyped about Signals like they have invented it. They have just copied this concept from different frameworks, nothing more.
Yes indeed they came from other frameworks. Still Angular adopting it is a good reason for hyping it. 😊 It's a major step forward for Angular. 👍