Is Angular changing TOO much?

The Angular team have released yet another RFC detailing the proposal for control flow syntax in template that is similar in style to Svelte. On top of all of the other changes we have seen recently, all of the changes coming to Angular might seem like a bit much.

#angular #signals #svelte

[NeroGming]

In germany we say "Lieber gut kopiert als schlecht erfunden" which means "It is better to copy in a good way, then invent something in a bad way". And that fits here perfectly

[adambickford]

Its starting to feel like java; there's 5 ways to do something but 3 are deprecated, 1 has fallen out of favor and the last is in preview.

[cab]

As someone who loves using Vue but is forced to use Angular for work, this is amazing.

[phennexion]

Awesome video, thanks for the great summary!!

[StephenMoreira]

I'm all on board with the changes. I don't do Svelte, but when Angular mentioned to change in syntax it took me 5 mins from, hmmmm another change. Ooooo you know what that is better, and probably more readable compared to what we are doing now.

[MattBodman]

Totally agree with your take on this. Nice summary!

[andimclean]

I've been playing with Signals and Standalone components in a private project and I love it. Can't wait for input and output signals.

[kylerjohnson]

Personally, I love the changes that are coming and I think they’re necessary if Angular is going to survive. People have long lamented the limited integration of RxJS within the framework itself. Signals solve that and in future releases it will dramatically improve change detection in Angular.

[timothydog]

Our company was coming from ExtJS and I pushed us towards Angular a couple years ago. Now we have multiple applications with Angular and I just finished up another (with a couple tips from Josh himself!). I really love seeing these changes in Angular because, as he says, I don't want Angular to become another ExtJS situation. I love having the ability to try new exciting features.

[JensChristianLarsen]

As a professional. it is not possible to keep up with Angular when working on a 100k+ cloc Angular project. It seems you always get stuck on a version near your starting point. However, as a hobbyist it's cool that the framework remains fresh.

[dracula]

i personally love OOP but when i tried angular was hard but seeing this new updates gonna try it again.

[ChrisPerko]

I agree. At first, I thought that the syntax seemed weird for angular, as we are used to HTML-like syntax. However, the benefits of cleaning up ngIfElse, ngSwitch, etc will be greatly appreciated. Also, not to mention, the mess that is ngFor trackBy. I never use it because the authoring experience is so bad 😜 (and let's face it, I forget to even use it)

[LarsRyeJeppesen]

noo these changes are so awesome! It's mindblowingly cool! loving it

[PatrikHorvatic]

A lot of changes, but very welcome ones. Keeping up with web dev trends keeps Angular alive

[nomiscph]

Love that we landed on the @ syntax its much cleaner

[abdulnafay]

The Signals are already out but still i didnt get a chance to use them and still alot changes are coming very awkward stage.

[GdeVseSvobodnyeNiki]

Not so sure about flow control syntax because it lacks nesting levels, but signal inputs is the feature i was waiting for.

[NeroGming]

I like to code, but I dont want to write a book. Less code I write, less code I have to read and understand. Both is good <3

[VyacheslavVyajev]

@JoshuaMorony Great video! Can you please tell me which vscode theme you are using?

[gipmhmf]

I totally agree that I’d rather have to update my codebase every once in a while to keep up with Angular improvements rather than stick to a stinky legacy framework. I’m really excited that the Angular team finally decided to improve the framework (and there’ a LOT of space for improvements there)