3:30 we were indeed asking for it.. For like 10 years.. Well thanks of course! But hopefully progress in Angular will no longer halt anymore like before.
Styling tab in the Angular Material documentation is huge. Angular Material was such a PITA to style properly - that lead to people starting using internal classes of Angular Material and getting burned pretty bad on updates. Also stoked about the schematic for theming. Honestly material-theming feel a bit overengineered. Like you have to pick 30 colors or something like that (3 colors with 10 hues) and angular material seems to use at most 10 of them in reality - possibly even less. (might be wrong here though ofc. No lie - it took me multiple hours to create a theme last time I tried because it was so weird and confusing. Will check this schematic out for sure. Awesome - Angular is getting even better.
Great update from Angular. I have a question. Is it still possible to use a custom svg icon in the recent version of Angular since NgModule is going obsolete? How should one implement it? HttpClientModule does seem deprecated or outdated as well when I tried to import it.
Hi! Great job with the framework. Has anyone else encountered an issue with when using incremental hydration? In Angular 19.0.6, components wrapped with @defer (hydrate on viewport) display an comment instead of the actual content after the build.
I love Angular, been using it for the past 6 years. But Angular doesn't love me back haha. I personally never found a job that would hire me as an Angular Front-end dev, not for a lack of trying. I just think that the market is not only quite small and exclusive, but also hyper-competitive. Sadly that's life. I still think the framework is great, intuitive, familiar and comfortable. It's just that with the job market as it is, it's too easy to lose hope and interest. For small, personal projects Angular works too, but might be seen as overkill in a lot of cases.
@@radicletech sure, so definitely take your time and use the features you'd like and the ones that benefit you. We do our best to keep the framework backwards compatible when releasing new features.
Years from now, you'll release another promotional video explaining how to get rid of these features you're presenting today as revolutionary, portraying them as obstacles to overcome-just like what happened with NgModules and other major shifts in the past. Are we stuck in a cycle of constant changes that complicate the development environment rather than simplifying it?
Standalone components are just a way to simplify NgModules. If you look at the 'Angular way' of creating NgModules, look at Angular Material. For example the MatButtonModule, it's just a component. But people use NgModules to bundle all of the code in a 'Shared' module that just makes the project bloated.
Im loving Angular 19 so much, thank you for the contents, maybe need some upgrades for we are here to help u guys!
New to angular, pushing to get an Angular job. wish me luck guys!
Good Luck, u will like it (:
All the very best. I am working on angular since last 6 year. I really enjoyed it!
Angular is very developer friendly than some tyrant library called react🤮. So you are on the right path.
Good luck
Angular team be working 24/7
@@o_glethorpe lol we are trying to build the best framework for the community
@Angular and you guys are doing a excellent job
2025 looks like a great year to learn angular, thank you
Yes it is a great time to be an angular developer. ❤
Angular team making waves!!!!!
@@timveseli 🌊🌊🌊
happy to be an angular developer when I see all that work from the Angular team :)
So glad to hear that! We're here fr the community :)
Let's pray angular material will some of theses days create something similar to a themed file upload component.
let's pray they will create something that's an actual competitor to primeng or kendo
Team Angular 🎉❤
You are all amazing
Great framework for enterprise projects❤
i love angular
Just watched it the second time and just now saw the resource signal. Gonna try this out right away damn
3:30 we were indeed asking for it.. For like 10 years.. Well thanks of course! But hopefully progress in Angular will no longer halt anymore like before.
Amazing bro
Styling tab in the Angular Material documentation is huge. Angular Material was such a PITA to style properly - that lead to people starting using internal classes of Angular Material and getting burned pretty bad on updates.
Also stoked about the schematic for theming. Honestly material-theming feel a bit overengineered. Like you have to pick 30 colors or something like that (3 colors with 10 hues) and angular material seems to use at most 10 of them in reality - possibly even less. (might be wrong here though ofc.
No lie - it took me multiple hours to create a theme last time I tried because it was so weird and confusing. Will check this schematic out for sure.
Awesome - Angular is getting even better.
Great update from Angular. I have a question. Is it still possible to use a custom svg icon in the recent version of Angular since NgModule is going obsolete? How should one implement it? HttpClientModule does seem deprecated or outdated as well when I tried to import it.
can anyone explain why you'd ever need the hydration feature?
Hi! Great job with the framework. Has anyone else encountered an issue with when using incremental hydration? In Angular 19.0.6, components wrapped with @defer (hydrate on viewport) display an comment instead of the actual content after the build.
resource is kinda weird because you still have to use rxjs for stuff like debounceTime
would love to some day be part of the angular team in google!
I love Angular, been using it for the past 6 years.
But Angular doesn't love me back haha.
I personally never found a job that would hire me as an Angular Front-end dev, not for a lack of trying. I just think that the market is not only quite small and exclusive, but also hyper-competitive. Sadly that's life.
I still think the framework is great, intuitive, familiar and comfortable.
It's just that with the job market as it is, it's too easy to lose hope and interest. For small, personal projects Angular works too, but might be seen as overkill in a lot of cases.
this could be overwhelming
@@radicletech sure, so definitely take your time and use the features you'd like and the ones that benefit you. We do our best to keep the framework backwards compatible when releasing new features.
THX, Angular is great... THX Google Staff for Google stuff : ))
Do you guys use AI to add these new features?
@@RehanKhan-xf3ml nope
I love Angular. But I'm stuck at V16😂.
speed up to counter. works well which Indian btw
Head is too small for all good things
Years from now, you'll release another promotional video explaining how to get rid of these features you're presenting today as revolutionary, portraying them as obstacles to overcome-just like what happened with NgModules and other major shifts in the past. Are we stuck in a cycle of constant changes that complicate the development environment rather than simplifying it?
intresting view
Standalone components are just a way to simplify NgModules. If you look at the 'Angular way' of creating NgModules, look at Angular Material. For example the MatButtonModule, it's just a component. But people use NgModules to bundle all of the code in a 'Shared' module that just makes the project bloated.
still vue
@@kostraone 🫡
@@Angular 👀🙏❤️