This New Angular Release Is Wild

Oh no, I'm talking about Angular again.

Seriously tho, this is dope and I'm hyped for the Angular community

S/O Ph4se0n3 for the awesome edit 🙏

[Soulis]

You thought you won. But now we've returned.- Darth Angular devs probably.

[stefankyriacou]

The best thing I always liked about when I used to work on an angular codebase, was that there wasn't really debates about what library to use, you just use angular.

[ShaharHarshuv]

As someone who is stuck with Angular for a while (and likely for a few more years) I've been super excited.
This is really not the channel to learn Angular from but there are other influencers that go over more changes.

[_dinesh]

Angular is the most intuitive framework/syntax. I have ever worked with. React on the other hand is a nightmare of useContext, useEffect and useState hooks which makes the code extremely hard to read the code.

[celiacasanovas]

I'm super hyped for Angular 17 and I think they're pointing at some really cool stuff that will get more fleshed out in subsequent versions. Angular 18-20 is gonna be great.

[flygonfiasco]

Having a program that expresses that “this happens then this happens then this happens” is imperative programming. Then he says declarative has been working for us as devs. Like, in the most common declarative language, SQL, you’re not gonna express the steps that are taken to get your data. You just tell it what you want and it just does it, it’s “implicit”, meaning the inner mechanics are abstracted away. I feel like these statements are contradictory. Does anyone have a different perspective on it? I hope I’m not misunderstanding him

[xxgunnery]

Working with Angular signals is the most comfortable front end dev experience I've had since I started. I still don't like fetching and dealing with external data in Angular, but once it's in the app through a service, it is LOVELY to pass around and compute things with signals.

[radvilardian]

The worst thing being an Angular developer is when you have new coworkers that was react developers join your team, and messes up your codebase. it is so pain when your boss prior features to be delivered as fast as possible, and these newcomers just throw a lot of messy codes in your previous works. Everything becomes fucked up when you comeback to your code. Another worse thing is your company dont even have someone who want to review your codes, just as long as you use angular which state to be very flexible in large projects. Well, that decisions fucked us apart, I hate being angular dev bcos of this .

[francoisguezengar]

I understand template can be annoying. But everything else is so much simpler than in react. Context is such a pain while injectable is so easy. useEffect is very limited compare to effect() or rxjs's operators. Form state / validation is very hard in react compare to FormModule. And more importantly directive is not a thing in react, you cannot compose component logic...
So overall I think, template declaration is a small price to pay to get all of this.

[avi]

I'm a React dev since it dropped in 2015. I was forced to lead an angular team for a project never having built a single app with Angular. We're also stuck on Angular 14 for reasons I shall not speak of. I gotta say, I thought it was going to be absolutely torture but in all honestly, *ahem* Angular is not *that* bad. React has many more weird "oh you gotta be an experienced React dev to know that" quirks to it than Angular. Theo talks about binding implicit behavior, but really how is that different than React hooks? It's an import and a wrapper bound to functionality that you have to know what it does and why and it's in no way explicit.

Angular feels very stable (it should but still). I think though, my opinion may have been different if it were Angular 13 which doesn't have standalone components. The NG Modules are just this whole entire other unnecessary layer of boilerplate (most of which still gets moved into the standalone component but at least it's not separate). I don't hate Angular. I don't see that team moving to v17 any time soon so I probably won't get to try out the latest features.

[thirdvectr]

Angular has always been goated because it makes you write code that's not a rats-tail mess

[PinkyZKey]

I have to rewatch this. I was admiring your earring for half the video on the first watch.

[jorgevaladas]

I've worked with Angular for a few years and at the time it always took long to onboard new people to the code base and the live reload was fairly slow. It's great to see the project improve and evolve to the point where performance and bloatedness may no longer be a concern.

When I went from Angular 2 to React (js, class components, prop-types) I honestly thought it was a downgrade in developer experience. React has come a long way since then and I wish the same to Angular.

[xav_]

Happy for the Angular community, it was well needed! I was also surprised to see Vue3 so performant on this benchmark. It's will be sexy as fuck to see what it can accomplish with a solid-like compiling strategy (Vapor mode)...😋

[SashaInTheCloud]

I am happy to see some positive change in Angular!

[JonathanLeeDev]

As an Angular dev, this is amazing to me! So excited for the future.

[moitp]

Nice from you to talk about it knowing you are not the biggest Angular fan.

But you clearly went too fast on that one and missed a lot of stuff.

The new control flow being probably the biggest miss. The perf screenshot you shown for example is when you use the new for loop provided by the new control flow. That has nothing to do with signals. They were able to improve it vecause they are not using the whole angular overhead from the template system. It's done in a way lower level.
They also added a @defer syntax that makes lazily loading parts of components very easy. That part especially will reduce a ton of boilerplate.

You also missed the implementation of esbuild / vite which will improve massively build / serve times that were always a negative part of the framework.

Looks like they are also starting to look at SSR more actively, meaning it will be probably interesting to follow their progress in next versions.

Plus they improved the v16 signals which are not experimental features anymore.

They improved the syntax for input / output aswel. Plus other less important updates.

Clearly, when they say it's "Angular Renaissance" they are clearly not lying. Since v15, they have done a lot of very nice improvements for DX. And they will keep doing it.

[yousafwazir]

Theo have you actually built a enterprise scale app with angular ? Seems you have not, speaks to your interests in REACT.

[EvanBoldt]

0:15 I haven’t seen a framework upend itself like this since Angular upended AngularJS.

[caIebthewood]

I'm learning angular for a new job so this is pretty amazing timing ☺️