Angular 19 is a BEAST of a release!

[@samithakulatilaka]

Thank you very much Max, as always. You're updates are concise and up to the point.

[@LarsRyeJeppesen]

Proud to have been the first person to suggest this standalone default, back right after V14 /s

[@agahuseynismayilov3955]

Hi Max. Thank you for the video. It would be great if you could prepare a fully project in Angular and explain it to us step by step. There are very few projects on the internet to learn better.

[@saiphaneeshk.h.5482]

Yeah, it's fine if they are a different course as well. Industry level projects using angular, or how to use angular with enterprise projects.

[@zygas15]

Angular is great frameworki. I have been using this for 5 Years

[@JayTailor45]

That’s what I also feel about Angular after using it for 5 years

[@PawePieczonka]

the same feeling, after 10 years :) (since angularjs 1.2)

[@ArchitecturalAesthetics2046]

very informative and clearly communicated. thank you.

[@eduardo2151]

Hello Max, will we have the version 19 course?

[@M3R14M.]

Hey Maximilian, I was looking into Stencil to build Web Components and make them compatible with Angular, React etc., but there hardly any videos out there on the topic. When I sorted by most views, I decided to watch the top result, despite it already being 7 years old at the time. I didn't look into who made it, well, color me surprised when I saw your face show up on my screen! Do you still use Stencil? I would love a follow-up on those videos, since much has changed in the past 7 years.

[@coder_one]

Read for yourself Ryan Carniato's articles "Web Components Are Not the Future" (creators of Solid.js) or Rich Harris (creators of Svelte) - they do an excellent job of dissecting this topic and arguing exceptionally substantively why web-components are a technology that has no future in web-development. If, on the other hand you care about creating components that are "framework-agnostic" then take a look at solutions like zag.js.

[@CancelOkay]

This is awesome. I've been waiting for this for ages. Gonnna fup tear down my react projects to angularrrrrrrrrrrrrrrrrrrrrrr.

[@WebGarmony]

Thanks for the info. As always, it was great!

[@cachabacha03ify]

Great video ! thx Max

[@paw565]

Modern angular is awesome.

[@joaosaraiva1998]

By modern angular you mean React? 🤣🤣🤣

[@paw565]

@joaosaraiva1998 I mean angular 17 or later. I hate things like modules or zone.js based reactivity. Fortunetly there are better tools in the framework.

[@punsmith]

​@@joaosaraiva1998 No kiddo, nobody but bootcamp babies loves react.

[@andyengle]

@@punsmith I wouldn't go that far. I learned React a long time ago, and I feel it's superior to Angular in many ways. It's far easier to be productive with React than Angular, and the market seems to agree. I'm not dissing it; by all means, use what you like, but there seem to be so many things to be aware of when working with it. Maybe too many things.

[@afrenchdude5331]

@andyengle I started by react and then moved to angular and I'm doing a bit of vue. The fact that react is easy to pick feels like a lure to me. It's very easy to ship something fast but way harder to maintain and you need a really good team of coordinated devs to not make a mess out of it. In the long run, I believe people waste a lot of time with this lib while they could have chosen a proper framework.

[@codelivewithme]

Im learning nest js old angular style backend framework i loved it for backend but on front end react &next js make lot sence

[@muzzi1984]

Modern Angular looks great anymore🚀👍

[@emrahumutkoc]

Max, sorry I couldn't watch the video on normal speed, it's a habit:))

[@usamasmr4621]

Hey max, i'm really confused between learning angular or next js, i like the opinionated side of angular to build large scale projects, but i like also the simplicity of next js to deliver very modern and good web apps, what do you suggest based on your experience and the job market currently?

[@afrenchdude5331]

It truly depends on where you live.

[@paw565]

Why not both? Choose a tool for the job.

[@usamasmr4621]

@@paw565 that's what i'm thinking right now, it's better to know both of them

[@theanswer1993]

If you want peace of mind when it comes to updating your projects and out of the box framework go with Angular. Thank me later.

[@LarsRyeJeppesen]

Both are very simple, it's up to you how to build. They are very similar.

[@Nilkamalsha75]

Can you please cover future of developer in midst of gen ai. How do we ensure ahead for future ready? What things can we learn ? Like node.js or just next.js or anything else. For react.js what is roadmap. Just react.js won't exists?

[@aparna603]

Wow!! Great news!!

[@KamoSevoyan]

You've forgotten to turn off your low speed mode dude :D. It's not Udemy, content size doesn't matter here.

[@mamedyahyayev4229]

Guys, does anybody know what is the tool he is using to draw shapes such as circles, rectangles and arrows

[@Alcaatraz01]

How do you feel about the lack of HMR support or update regarding it? Despite the awesome application features, it's miserable to actually write code when the browser has heavy full page reloads. Just can't recommend it to anyone until that's addressed. Even NextJS with their nuclear custom tool chain is doing it better...

[@SirLino]

Good news! In the release post, there’s some notes on the HMR support for styles and on the experimental template HMR that’s part of v19.

[@StingSting844]

Hmr is hard to get right when you have too many moving parts. And angular is famous for too many moving parts and opinions

[@marcuss.abildskov7175]

HMR is overrated.

[@Alcaatraz01]

@@marcuss.abildskov7175 Yeah OK

[@LarsRyeJeppesen]

Angular v19 has HRM for scss and templates. Not sure how you missed that?

[@madeOfClay99]

So since version 19 components, pipes, directives, etc... are going to be standalone, that means we don't have to attach the "imports" property as well? We can simply use whatever we need in our components without importing dependencies, like CommonModule, async pipe, etc...?

[@paw565]

You have to import standalone pipes, components etc

[@madeOfClay99]

So the only thing that now is default is standalone: true? But we have to keep using the imports array in our standalone components? I thought that since is defaulted as true, the imports array in the component's metadata is no longer used...

[@LarsRyeJeppesen]

No that is not the case. It might come later. I do like the imports though, it's very explicit of what is used. If I import a ton of stuff I don't use, then it gets confusing to figure out what you use and what not.

[@keerthivasan764]

Does angular material also new version released

[@valothfamily4901]

Thank you very much for the update on Angular 19. I am seeing a trend towards react.js, is this observed by everyone? Is there any reason for this shift towards react.js?

[@theanswer1993]

Too many bad bootcamp developers that can't learn Angular.

[@paperell]

standalone were the default already in v18 though??? Anyway, now that angular is really good and nice (it has been since v17) I guess it's time for google to kill it. RIP

[@LarsRyeJeppesen]

No there were not. You had to use the "standalone: " property in all components.

[@kennedymwenda3357]

No Runtime Configs yet?

[@LarsRyeJeppesen]

Damn, React noobs feeling the burn in the comment section.. calm down girls, it doesn't affect you, keep using your beginner friendly "framework"

[@yasminarab1353]

Danke sehr

[@JokeryEU]

i have a problem when updating from v15 to 18 and later, no error on build or run, but on console in browser i get couldn't read configuration, and the page is blank

[@ggcc3261]

I'd like to use it but no equivalent of shadcn/ui makes it a no-go for me as I always start with that or something like MUI which is time tested and mature.

[@sealone777]

Where’s HMR?

[@TightyWhities94]

why would you make a component non-standalone?

[@TheNsn666]

If you need to migrate modules code which have components that are not standalone, you will need to mark them as non standalone...

[@TightyWhities94]

@TheNsn666 Just make everything standalone by default and remove marking. We are adding unnecessary modularization with this.

[@TheNsn666]

@@TightyWhities94 Yes but sometimes in your codebase (many companies) you cant change every thing and just migrate all code, so if you still want to use v19 you must mark components.

[@theanswer1993]

R.I.P. React

[@KamuranDehliz]

I don't really understand angulars implemention of Signals. Preact seems to do it better

[@LarsRyeJeppesen]

Not really

[@andyengle]

Maybe it's just me, but I am not an Angular fan. I've been working with React since probably 2017, but with Angular for the last 6 months. I'm trying to give it a go, but I'm just not a fan. Several things bother me about it, specifically, the whole thing with TS, HTML, and CSS files being broken apart. Is that necessary? Working with props seems like a hassle, and then there's the whole thing of responding to prop changes and knowing when to render updates. React makes all of this very easy, but Angular makes you jump through hoops. Is there something I'm missing? Generally, this framework makes me work a lot harder for what I can do a lot easier with React.

[@SXsoft99]

Breaking functionality, templating and style isn't a bad ideea, when you have a big code block for that specific component

[@andyengle]

@SXsoft99 Ok, I can see that. In React world, we would just break that down into smaller components and compose from there.

[@LarsRyeJeppesen]

It's not necessary. By all means ,use the same file

[@hsil408]

👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼👏🏼

[@Cero-d5z]

Verbessere mal dein Angular Udem-Kurs . Der ist unübersichtlich

[@ZAcharyIndy]

I was adopter since the v1. When v2 came out , I just threw it to the trash. No thanks, I moved to Svelte. Faster, simpler, simply amazing and useful.

[@SharunKumar]

React 19 > Angular 19

[@khanra17]

🗿Title 🤡Video

[@babakfp]

When I hear about frontend frameworks, I just want to 🤢🤢... I'm sick of all of their bs...

[@billy8461]

no thanks will stick to react

[@curiousprogrammer90]

Angular looks awful. I am sad for poeple working with it lol...

[@LarsRyeJeppesen]

how so? are you a child?

[@darahk88]

tomorrow google will shut it down like flutter and any other projects. google products are not stable for long term

[@theanswer1993]

Angular has been going for longer than React my friend.

[@sng8240]

If I'm not mistaken, Google is trying to unify Angular with the framework they use internally, in my opinion, the future of Angular is good. In the case of React, they have been trying for years to release React 19 and many derivative frameworks have been impacted by this while Angular continues to evolve without compromising backwards compatibility and making it easier to adopt new versions.

[@darahk88]

@ React also has some braking changes that current libraries must update. It means we can’t use current AI tools to generate code

[@LarsRyeJeppesen]

Angular is older than React... lmao

[@theanswer1993]

@@LarsRyeJeppesen Angular JS was released in 2010 and then updated to Angular in 2016. React was released in 2013. So yes Angular is out there for 3 years longer.

[@igorr4682]

Future of Angular ? Is there still a future for this platform?

[@punsmith]

Lol you can use react if you want. Oh wait, not even the react team considers it a good idea to use react without a meta framework. Go play in your react sandbox.

[@LarsRyeJeppesen]

Why are you even here? Go back to your React, noobie :)

[@bakasenpaidesu]

.