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.

▲

Klaster_1 5 hours ago | parent | next [-]

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.

▲

spankalee 4 hours ago | parent [-]

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.

	▲	embedding-shape 3 hours ago \| parent \| next [-]
		"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.
	▲	bpavuk 4 hours ago \| parent \| prev [-]
		[dead]

▲

majora2007 3 hours ago | parent | prev | next [-]

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.

▲

mhitza 4 hours ago | parent | prev [-]

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?

▲

jonkoops 3 hours ago | parent | next [-]

I believe Signals are the go-to now, but surely RxJS is still present for complex use cases. Are Zones fully gone?

▲

vyrotek 3 hours ago | parent | next [-]

As of v21, zoneless is the default

https://angular.love/angular-21-whats-new

	▲	jonkoops 2 hours ago \| parent [-]
		Nice

▲

andriy_koval 3 hours ago | parent | prev [-]

Now we have promises, observables and signals.

I would be more happy if it would be just one of those..

	▲	halflife an hour ago \| parent [-]
		Each one of these solves a different problem. Promised - async Observables - streams Signals - reactivity

▲

thevillagechief 4 hours ago | parent | prev | next [-]

Everything is signals now.

▲

throw310822 2 hours ago | parent | prev [-]

The problem with Angular is that the http client service used to return observables by default and that made people think that you had to use them as such. It was a mostly useless, massive pain. Working with Angular became a pleasure the moment we decided to just cast our service calls to promises.

For the rest, RxJS is cool where you actually need it and want it.