Really excited for this. I've been dying to use signal-forms and resources since they were experimental. Once I got on the signal train, I could never go back and having to use RxJS for forms became a major pain point.
<p><pre><code> import {signal} from "@angular/core"
import {form} from "@angular/forms/signals"
</code></pre>
So, signal comes out of core and form comes out of forms/signals. This must be a terminology thing I don't get.<p>Other than that. Looking forward to try Angular again after a decade of absence. I think it looks pretty good.
Wow Angular Aria looks fantastic. Even have full docs for the more complicated scenarios like autocomplete. Can't wait to get this in my hands and see if it replaces the custom screen reader autocomplete I had to make.
Maybe I'm dumb, but I go to: <a href="https://angular.dev/guide/aria/overview#showcase" rel="nofollow">https://angular.dev/guide/aria/overview#showcase</a> and try out the keyboard controls, somehow they've decided that those elements should be navigated with the arrow keys instead of much more commonly used tab and shift+tab? Even the tabs from their own documentation, right above that example, also uses tab/shift-tab for moving focus between them.
I must admit, modern angular has been a pleasure to use. It's a shame that the ecosystem is a little rough. Luckily you get so much out of the box already.
Same experience here.<p>I wish Angular dropped their weird compiler that's tight coupled to tsc and moved into more pluggable approach so you can use it with whatever TS compiler. App and unit test cold build times are still crap, but at least with a coding agent you care about this less.
What is rough in the ecosystem? I haven't had any issues finding packages. Most packages have been keeping up with the signal trends as well.
Are projects still chosing to pick RxJS (or equivalent) which make the code heavily layered and a pain to debug?<p>Or has sanity reached the Angular ecosystem by now?
I believe Signals are the go-to now, but surely RxJS is still present for complex use cases. Are Zones fully gone?
Now we have promises, observables and signals.<p>I would be more happy if it would be just one of those..
As of v21, zoneless is the default<p><a href="https://angular.love/angular-21-whats-new" rel="nofollow">https://angular.love/angular-21-whats-new</a>
Everything is signals now.
Angular has made my programming career joy and it has not felt like work at all, all the best to angular dev team! Nothing better than getting to work with favorite language, learning better and getting paid :D
I like Angular, it feels a bit like Django. Easy to use with everything included.
Overkill. React mogs.
the biggest problem in angular is that it is so hard to use a custom toolchain, i.e. not their angular/cli product instead mix it with other stuff in lets say vite
What kinds of features or workflows are you missing that Angular's CLI doesn't cover? Or is it just that you're used to Vite (or something else) and wish you could use that instead of Angular's own tooling?<p>I'm not on the Angular development team or anything, though I do use Angular at $DAY_JOB and I'm overall perfectly fine with the framework and its tooling. However, the grass might be greener elsewhere; I'm just not familiar with it!
for many people this is the biggest bonus
Seems like Angular has gotten better since v2 (my last experience).<p>Has anyone done a modern Angular vs. React comparison that's not an AI slop article?<p>I'm also curious if it's "simple made easy" for performant applications. React is arguably "simple made hard", but there are notable, highly performant applications written with it (Linear comes to mind).
Angular Control Flow alone is a massive QoL improvement compared to the React way to do template conditions, switches, loops, etc.<p><a href="https://angular.dev/guide/templates/control-flow" rel="nofollow">https://angular.dev/guide/templates/control-flow</a>
Modern Angular is MUCH nicer to use than the v2 days (or even the v4 days when I first started working with it). A lot of the required boilerplate is unnecessary nowadays. And even RxJS and NgRX are becoming less and less necessary to use too, which is great.
Using angular in 2026 is mad :D
When I look at job postings and see "React" I go "ugh" these days and find myself looking for Angular instead. That's the complete opposite of my thoughts from just two years ago.<p>I would still rather use something else (instead or React or Angular) but 1) most jobs in my area are asking for one of those, and 2) I'm actually starting to lean towards Angular even for personal projects.<p>Angular is great these days, and they're making really nice improvements.
Have you used it in the last 8 years? Its actually quite a good piece of software.