Having used every version from 1, 2, 4 - 16 , This video is absolutely clickbait as it is NOT a completely different framework. What are you comparing it to? version 1? Some neat new features, but again NOTHING revolutionary. Recruiters will be asking "How many years do you have working with Angular 17?!" SMH Do better.
ปีที่แล้ว +4
BDE pinning this comment ngl. For what it's worth, Signal+Computed+Effect, and new control flow are pretty big game changers, it reminds me a lot of Vue.js.
I recently updated an application made with Angular v14 to v17, and I was able to reduce a large part of the code, minimize loading and rendering times by more than half, incorporate greater reactivity and functions, in addition to having cleaner, more readable and scalable code. The difference results are abysmal with the new implementations. In short, it provides much more control without loading the application with unnecessary weight and maintains this performance thanks to its focused change detection.
I will say modern angular in my opinion is by far the easiest framework to control state in. I’ve never felt the need to bring in a third party library.
@@awesome-coding Solid is currently my favorite framework, but I still like sharing state with services and behavior subjects/ observables more than context. That being said I enjoy signals on the component end of things far more.
It is definitely one of the most powerful updates from Angular so far. The new syntax looks cleaner and especially since no import is necessary. @defer is a big win and so the default with esbuild + vite. Nice video btw 👍
Been using the standalone components although they have been in the background for a few versions to be fair. I forgot about the new template structures, I will start to incorporate them soon!
Can someone please explain me , what us state in angular and why we use it and how it works .... I found in my company git repo , but couldn't figure out why they used caching and also state
Gotta love the comments. Some people simply want to rag on Angular. Just Angular Animations alone murders most frameworks in how powerful it is. Easily best form builder to date. Signals? Peak engineering. Thanks to services you never need a cumbersome state library again.
I think the main issue is that there are a lot of other alternatives for Angular, most of them with a simpler DX. A lot of frameworks were offering Signals for reactivity before angular did, and tools like Solid or Svelte come packed with native store solutions which one might argue are more elegant than services. I believe Angular has the same image issues like Java. It is a great, powerful tool, but since it is heavily used in enterprise and big projects it is also easier to be hated.
LOL, I was wondering about the up & down sing-songy voice too. It's very distracting so i slow down the speed & turn-on subtitles. I'm still jealous of multilingual people however, since I have a hard time with just English. Pretty good little video tho, its impressive folks put time & effort into training for others.
The only thing though, >90% established Angular projects are not going to ever upgrade to newer style because it's just too much maintenance work for most devs.
They have schematics in the CLI which automatically upgrades all the code for you. Also all the old primitives still work in the newest version of course.
Experienced developers will continue with the old and reliable one. New developers won't use Angular because its new version isnt popular enough to provide jobs.
That is not really true, as a lot of work is done in the realm of schematics. I upgraded a large Angular app to the new control flow in about 30 minutes, thanks to schematics. I think the most important "feature" is the upgrading process we have since Angular version 2
always use the latest version, as most Angular projects are max a few month behind the latest version. If you get a job for a outdated version (e.g. more than 4 versions behind the current) I would question if the company is good or if there is a lot of issues in the code base
Why not just embrace jsx instead of control flow? Templating syntaxes always leave functionality to be desired and often dont translate to other frameworks. Jsx also has full TS support already.
@@awesome-codingI am one of them. Templating language should be just that not a programming language, it should be declarative and declarative only. Ive been doing web dev for a looooong time trust me writing js in your templates is fine but when js IS your template it will not be very maintainable in the long run
@@TechBuddy_ i think the concern for me arises when you need more and more logic to express your template. For instance, i come from a vue background. In vue, if you want go template out a for loop, you only have 1 option, v-for which is for a forEach loop. What if i want to iterate in reverse? Or access items outside of the for loop scope? I have to start doing a bunch of wonky overhead to prepare the forEach loop to really not do what its declaring it does. Im not a fan of react because of how it handles everything else, but i think jsx is the right direction
@@hamm8934 that's what I am talking about "your template should be declarative" if you want to iterate a list in reverse create a new computed property ( be it vue, angular, svelte or whatever it is ). Your v for should only tell what to iterate not how to iterate
@@TechBuddy_ I see what youre saying. I guess ill have to think about it more, and maybe its because i havent used jsx professionally, but from my experience in vue, i find having to do a bunch of computed overhead to prepare the v-for array creates less declarative code overall. Sure, the templating is declarative, but i think this overall produces more imperative code for the overall component. It also often feels a little hacky to do. Ill have to play around with jsx more
lmfao you should also remember class-based React -> functional components -> hooks -> server components And whatever the current "trendy", oh sorry, "industry standard" state management toolkit is.
@@xucongzhan9151 "class-based -> hooks + functional components transition" in React is a fair argument, even if does not really compare in pain/suffering, since class based react components are still supported to this day (even in React 18 and in SSR) and Angular 1 is not. "industry standard" state management toolkit is not really a good argument, since pretty much any of jotai, zustand and every other popular react state manager is good as well, because everyone of them provides signal based implementation. So you can pick either one and be contend.
I know it's a meme to hate Angular in React world, but the Angular team has been working hard to update and also be backward compatible, please give a quick look again.
@@davidsiewert8649 Angular 1 and 2 are completely different frameworks though, even different npm and github repo, from Angular 2 to now it's the same framework. So you can't compare different versions of React and say it's the same as 2 different frameworks.
No, they dont remove the old syntax, they "only" add new stuff, so people can update angular version, without the NEED of chaning all their code.... they CAN adapt to the new style :)
is very different, the perspective moved from modules to stanalone components, change detection stopped depending on zonejs to now be focused on the component that renders the change, many features went from being classes to being functional .ts files, in addition to faster rendering speed and lightweight applications and greater control of lazyload codes, routes and components.
That's a major update but still a meh framework imo... Honestly i find that angular wasn't designed to be the default framework for modern web development, i believe it's more suitable for corporations
Can you define modern web development please ? Because if you say something like this without any context it feels like you are repeating the words of some other person without any nuance
Omg, with all these directives and bloated syntax I cannot say I can like this angular ever 😂😅 Even react is simpler though I prefer the Solid.js these days
@@TayambaMwanza haha, 100%. Also @if, @for is so much cleaner (and intuitive for new users) than jsx ternaries and mapping. Sure, Angular has some bloat in some areas, but things like this by far make up for it.
Having used every version from 1, 2, 4 - 16 , This video is absolutely clickbait as it is NOT a completely different framework. What are you comparing it to? version 1? Some neat new features, but again NOTHING revolutionary. Recruiters will be asking "How many years do you have working with Angular 17?!" SMH Do better.
BDE pinning this comment ngl. For what it's worth, Signal+Computed+Effect, and new control flow are pretty big game changers, it reminds me a lot of Vue.js.
and if we're honest the @ handlebars is really just directives
I recently updated an application made with Angular v14 to v17, and I was able to reduce a large part of the code, minimize loading and rendering times by more than half, incorporate greater reactivity and functions, in addition to having cleaner, more readable and scalable code. The difference results are abysmal with the new implementations. In short, it provides much more control without loading the application with unnecessary weight and maintains this performance thanks to its focused change detection.
I will say modern angular in my opinion is by far the easiest framework to control state in. I’ve never felt the need to bring in a third party library.
Have you tried Solid?
@@awesome-codinglol I wanted to say sveltekit but solid and solidstart is awesome too 😅
@@awesome-coding Solid is currently my favorite framework, but I still like sharing state with services and behavior subjects/ observables more than context. That being said I enjoy signals on the component end of things far more.
what about svelte?
It is definitely one of the most powerful updates from Angular so far. The new syntax looks cleaner and especially since no import is necessary. @defer is a big win and so the default with esbuild + vite. Nice video btw 👍
Thank you!
That was quite masterful I wish you had kept this going for another 1 hour using the same format.
Thank you! It really means a lot!
Been using the standalone components although they have been in the background for a few versions to be fair.
I forgot about the new template structures, I will start to incorporate them soon!
Thanks for the quick overview, the whole reason angular changed its logo is to say they are in a new Era, so this changes are just the start.
That was a great summary. Concise and very informative! Thanks!
Glad it was helpful!
Angular is awesome
Can someone please explain me , what us state in angular and why we use it and how it works .... I found in my company git repo , but couldn't figure out why they used caching and also state
Gotta love the comments. Some people simply want to rag on Angular. Just Angular Animations alone murders most frameworks in how powerful it is. Easily best form builder to date. Signals? Peak engineering. Thanks to services you never need a cumbersome state library again.
I think the main issue is that there are a lot of other alternatives for Angular, most of them with a simpler DX. A lot of frameworks were offering Signals for reactivity before angular did, and tools like Solid or Svelte come packed with native store solutions which one might argue are more elegant than services.
I believe Angular has the same image issues like Java. It is a great, powerful tool, but since it is heavily used in enterprise and big projects it is also easier to be hated.
Could you please explain how can we import previous NgModules into new v17 app.
You can use the "imports" tag, just like I did in the video.
Whats this song you use in the videos?
LOL, I was wondering about the up & down sing-songy voice too. It's very distracting so i slow down the speed & turn-on subtitles. I'm still jealous of multilingual people however, since I have a hard time with just English. Pretty good little video tho, its impressive folks put time & effort into training for others.
bro what is this code editor
plzz tell me
feels like fleet
i don't think that's an IDE, it's just an edited image with the screenshotted code
Right - It's an edit, but the font and styles are from the IntelliJ IDEA editor.
Try neovim you can make it look like this or whatever you feel like
The only thing though, >90% established Angular projects are not going to ever upgrade to newer style because it's just too much maintenance work for most devs.
That's true. However you have a huge number of experienced developers who'll have access to much better tools when they'll start the next project.
They have schematics in the CLI which automatically upgrades all the code for you. Also all the old primitives still work in the newest version of course.
Experienced developers will continue with the old and reliable one. New developers won't use Angular because its new version isnt popular enough to provide jobs.
@@prohacker5086 yes, I think the same. Angular is more of a chore for new developers.
That is not really true, as a lot of work is done in the realm of schematics. I upgraded a large Angular app to the new control flow in about 30 minutes, thanks to schematics.
I think the most important "feature" is the upgrading process we have since Angular version 2
Should i learn angular 16 or 17??? Please give me an advise! I am new at angular
always use the latest version, as most Angular projects are max a few month behind the latest version. If you get a job for a outdated version (e.g. more than 4 versions behind the current) I would question if the company is good or if there is a lot of issues in the code base
Exactly what @chaos_monster said. Of course, focus on the basics & the core ideas first, but always target the most recent versions.
You can have single file components in angular and it’s still much better than jsx
Looks like Angular got a hand on that footgun
Funny! 😂
Interesting, however it sounds like you are confusing Server Side Rendering (SSR) with deferred loading 🤷♂
Sorry if it seems like that. I just meant that both are useful tools to improve initial loading times and the UX.
I've been following sarah on x from a long time and the new angular is very good from what I've seen and heard
Why not just embrace jsx instead of control flow? Templating syntaxes always leave functionality to be desired and often dont translate to other frameworks. Jsx also has full TS support already.
Coming mostly from a React background I agree. However, there are A LOT of people out there who dislike JSX.
@@awesome-codingI am one of them. Templating language should be just that not a programming language, it should be declarative and declarative only. Ive been doing web dev for a looooong time trust me writing js in your templates is fine but when js IS your template it will not be very maintainable in the long run
@@TechBuddy_ i think the concern for me arises when you need more and more logic to express your template. For instance, i come from a vue background. In vue, if you want go template out a for loop, you only have 1 option, v-for which is for a forEach loop.
What if i want to iterate in reverse? Or access items outside of the for loop scope? I have to start doing a bunch of wonky overhead to prepare the forEach loop to really not do what its declaring it does.
Im not a fan of react because of how it handles everything else, but i think jsx is the right direction
@@hamm8934 that's what I am talking about "your template should be declarative" if you want to iterate a list in reverse create a new computed property ( be it vue, angular, svelte or whatever it is ). Your v for should only tell what to iterate not how to iterate
@@TechBuddy_ I see what youre saying. I guess ill have to think about it more, and maybe its because i havent used jsx professionally, but from my experience in vue, i find having to do a bunch of computed overhead to prepare the v-for array creates less declarative code overall. Sure, the templating is declarative, but i think this overall produces more imperative code for the overall component. It also often feels a little hacky to do.
Ill have to play around with jsx more
Sometimes it feels like the author of the video starts talking in Spanish 😂
As a Spanish myself, I don’t understand 😂
You mean that something you don’t know what tf he’s saying?
For that kind of expression we use Chinese instead, just a curious fact.
And in turkey I think they use greek
@@greyshopleskin2315hes saying that because the narrator is speaking a bit too fast in some points
I'm just trying to appeal to a larger, international audience! 😅
So I'm from East Europe, speaking English and sounding Spanish :)
@@awesome-codingI'm Slavic myself so I understand. But a Balkan Slav
Is this like firebase? I'm subscribing expecting it!
I wish I could deliver the same quality 😅
Sees Angular 17, remember Angular 1 & 2, shudders, goes back to React
lmfao you should also remember class-based React -> functional components -> hooks -> server components
And whatever the current "trendy", oh sorry, "industry standard" state management toolkit is.
@@xucongzhan9151
"class-based -> hooks + functional components transition" in React is a fair argument,
even if does not really compare in pain/suffering, since class based react components are still supported to this day (even in React 18 and in SSR)
and Angular 1 is not.
"industry standard" state management toolkit is not really a good argument, since pretty much any of
jotai, zustand and every other popular react state manager is good as well,
because everyone of them provides signal based implementation.
So you can pick either one and be contend.
I know it's a meme to hate Angular in React world, but the Angular team has been working hard to update and also be backward compatible, please give a quick look again.
It's been 15 versions and years since angular 2 💀 that's not just shudders at this point that's PTSD
@@davidsiewert8649 Angular 1 and 2 are completely different frameworks though, even different npm and github repo, from Angular 2 to now it's the same framework.
So you can't compare different versions of React and say it's the same as 2 different frameworks.
Again? Seriously?
No, they dont remove the old syntax, they "only" add new stuff, so people can update angular version, without the NEED of chaning all their code.... they CAN adapt to the new style :)
Hello senior angular developers. Congratulations you become a jenior developer again 🤦. Technology sucks
😂
Learning this is light work, automatic migrations, no headache whatsoever.
The Angular team was sure to make this update as painless as possible
These new features look really easy to pick up
Is not different only have new features
I would argue that the new features are so impactful that it is changing the entire framework moving forward.
is very different, the perspective moved from modules to stanalone components, change detection stopped depending on zonejs to now be focused on the component that renders the change, many features went from being classes to being functional .ts files, in addition to faster rendering speed and lightweight applications and greater control of lazyload codes, routes and components.
That's a major update but still a meh framework imo... Honestly i find that angular wasn't designed to be the default framework for modern web development, i believe it's more suitable for corporations
What's your preferred framework?
Can you define modern web development please ? Because if you say something like this without any context it feels like you are repeating the words of some other person without any nuance
@@awesome-coding astro is my favorite, but i tend to use Next/React most of the time, i really enjoy working with them as well
Angular has a lot of good tools to enable data-driven design patterns, but it’s honestly suitable for all sorts of development imo.
not clean like svletekit :))
That's true :)
You know I want to agree with you sooo hard right now but at the same time the new angular feels very very cool
Crazy how all frameworks are just copying what Svelte did 2~3 years ago...
I don't really agree with this one 😅
Next Js is the king 👑 period.
🤮
I like Angular, but i have to admit that being able to do backend API Node stuff in the same project code is really nice. :)
Omg, with all these directives and bloated syntax I cannot say I can like this angular ever 😂😅
Even react is simpler though I prefer the Solid.js these days
Bloated syntax?
React:
const [count, setCount] = useStat(0);
Angular
count = signal(0);
Non Signal Angular
count = 0;
@@TayambaMwanza haha, 100%. Also @if, @for is so much cleaner (and intuitive for new users) than jsx ternaries and mapping. Sure, Angular has some bloat in some areas, but things like this by far make up for it.
I don't like the new syntax of directives @for, it reminds me of Razor. I loved using *ngfor
Fair enough!