Using angular in 2026 is mad :D
Have you used it in the last 8 years? Its actually quite a good piece of software.
Angular v22
21–30 of 84 posts
Re: Angular v22
#22Wow 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: https://angular.dev/guide/aria/overview#showcase 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.
Re: Angular v22
#23Earlier quoted context omitted.
Same experience here. 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.
Angular should ditch the compiler altogether - it really hinders them in so many ways, especially now with AI-codegen where tools have to specifically choose to do the work to integrate the Angular toolchain instead of using plain TypeScript and HTML.
"plain TypeScript"? Just like Angular, TypeScript depends on a compiler too, regardless of where in your toolchain it is, unless I missed browsers somehow being able to straight up run TypeScript nowadays. Bit ironic to cite "ditch the compiler" as the reason to switch from one compiler to another.
Re: Angular v22
#24I 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.
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.
Re: Angular v22
#25Really 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.
Re: Angular v22
#26Overkill. React mogs.
Re: Angular v22
#27 import {signal} from "@angular/core"
import {form} from "@angular/forms/signals"
Other than that. Looking forward to try Angular again after a decade of absence. I think it looks pretty good.
Re: Angular v22
#28import {signal} from "@angular/core" import {form} from "@angular/forms/signals" So, signal comes out of core and form comes out of forms/signals. This must be a terminology thing I don't get. Other than that. Looking forward to try Angular again after a decade of absence. I think it looks pretty good.
There are a lot of ways to do Forms in Angular. I assume that's importing the new "Signals" based form.
Re: Angular v22
#29Earlier quoted context omitted.
Are projects still chosing to pick RxJS (or equivalent) which make the code heavily layered and a pain to debug? 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.
I would be more happy if it would be just one of those..
Re: Angular v22
#30Using 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.
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.
Angular is great these days, and they're making really nice improvements.