Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular v22

blog.angular.dev

Post reply on HN
Print view View original

31–40 of 84 posts

Re: Angular v22

#31

Post by throw310822 »

mhitza wrote: post #5
vyrotek wrote: post #2

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.

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?

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.

Re: Angular v22

#33

Post by darkteflon »

majora2007 wrote: post #25

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.

Could you say more about signals? Is it are all analogous to, say, game engine signals paradigms (eg Godot) - components at any depth emit signals and any other component can subscribe? Or something totally different?

Re: Angular v22

#34

Post by majora2007 »

pan69 wrote: post #27

import {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.

Signals are a privative data structure in Angular, hence core. Signal-based forms are part of the Forms module. You aren't using forms, you don't get the overhead.

Re: Angular v22

#35

Post by halflife »

andriy_koval wrote: post #29
jonkoops wrote: post #10

Earlier quoted context omitted.

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..

Each one of these solves a different problem.

Promised - async

Observables - streams

Signals - reactivity

Re: Angular v22

#37

Post by exac »

majora2007 wrote: post #34
pan69 wrote: post #27

import {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.

Signals are a privative data structure in Angular, hence core. Signal-based forms are part of the Forms module. You aren't using forms, you don't get the overhead.

primitive

Re: Angular v22

#39

Post by shay_ker »

vyrotek wrote: post #20
shay_ker wrote: post #8

Seems 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. https://angular.dev/guide/templates/control-flow

I do wonder - why not add this to jsx?

Re: Angular v22

#40

Post by woodpanel »

Out of curiosity I’ve progressed away from Angular around 2018. My peak spa-ish reduxian state management experience was building an NgRX combo with @ngrx/effects for side effects.

Till this day I remember this fondly as it gave me so much ease of control of the application’s many complex states. Especially when I nowadays deal with all sorts of false-prophets in forms of hooks and what ever reactive primitive du-jour (don’t get Me wrong they are 80% of the time the better choice, it’s just that they don’t scale).

What’s today’s version of complex state management in Angular-Land?

Post reply on HN