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
Angular v22
11–20 of 84 posts
Re: Angular v22
#12Using angular in 2026 is mad :D
Re: Angular v22
#13I like Angular, it feels a bit like Django. Easy to use with everything included.
Or I mean, you could just use Django (or some faster backend with templating and SSR). Using that with htmx you get the SPA experience and still without the madness of an actual rotten JS ecosystem.
Re: Angular v22
#14Angular 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
Re: Angular v22
#15the 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?
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!
Re: Angular v22
#16Seems like Angular has gotten better since v2 (my last experience). Has anyone done a modern Angular vs. React comparison that's not an AI slop article? 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).
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.
Re: Angular v22
#17Earlier 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?
As of v21, zoneless is the default
Re: Angular v22
#18the 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
for many people this is the biggest bonus
Re: Angular v22
#19Wow 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.
Re: Angular v22
#20Seems like Angular has gotten better since v2 (my last experience). Has anyone done a modern Angular vs. React comparison that's not an AI slop article? 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.