The latest on Zoneless in Angular v18

We’re one step closer to building a zone.js optional for Angular applications. Alex, a Technical Lead for Angular Framework shares what’s more to do to make this a reality, where we are so far, and the future of zone.js.
Watch more Angularv18 → goo.gle/Angularv18
Subscribe to the Angular channel → goo.gle/Angular
#Angular #AngularV18
Speaker: Alex Rickabaugh

[@jeter550]

O angular mais vivo do que nunca! Comecei um projeto com angular 17 em setembro de 2023 para uma instituição do terceiro setor aqui no Brasil. E hoje podendo ver o lançamento da versão 18 fiquei muito feliz por ter feito a escolha certa!

[@kedevked]

Over a decade ago, Angular emerged as a leader in frontend frameworks. Its upcoming embrace of signals has the potential to be a game-changer for frontend development, offering a more reactive and efficient approach to building web applications.

[@LarsRyeJeppesen]

We went zoneless, amazing stuff

[@tomastrajan]

Zoneless is MVP for the Angular based public facing websites !

[@dmitrykomkov8480]

I want to remind to people in the comments, that rxjs is an implementation of Reactive Extention from Microsoft. It was invented to build Reactive Systems, not Reactive Frontend Application. Before the Signals we did not have better approach to handle derived state and used rxjs. Now we use Signals for derived state. But it does not mean we should get rid of rxjs today. Its still the best tool for event management.

[@KostasOreopoulos]

Probably the Subject and Behavior part of Rxjs are now obsolete (or at least I do not find a reason to use them, except the part that Angular uses behind the scenes to convert observables to signals). Everything else is fully useful and works perfectly with signals.

[@sulaimantriarjo8097]

So long journey. congrats

[@codewithpushpa]

Very good !

[@sameralkhatib4474]

Is on push change detection strategy needed when going zoneless?

[@xucongzhan9151]

iirc, yes. When signal components drop I think it's not needed for *them*, but still required for other non-signal components.

[@amosisaila8416]

Exit the zone!

[@tarasshpek]

As a backed dev, I chose Angular specificly because of zone.js. The idea that you can map JS object's field to the part of template and framework will do the job is AMAZING. I'm not against signals, but I hope you'll keep the zone.js as part of Angular.

[@AlainBoudard]

What would zone do for what you describe ? I fail to understand.

[@MichaelSmallDev]

FORMS + SIGNALS MENTIONED ❗❗❗

[@Sara-xi2ug]

I've heard that signals may become part of Javascript? What's going to happen to Angular signals then? Thanks

[@AlainBoudard]

Just like other js frameworks did before, if the native implementation is sufficient, they would eventualy drop their own. That's only my guess :)

[@mxz2024]

how should i use formgroups now with signals?

[@Versus-A]

How does the hybrid change detection work? Does it bring any benefit to use it in a half signal half zone app or it's worse in terms of performance?

[@GerardoBuenrostro]

Is a stable virtual scroll in the future? Because right now is a nightmare.

[@jonathangamble]

Any plans to actually support server only routes… its crazy to me I can’t do this like every other framework

[@mrika1995]

use analogjs for that

[@tarquin161234]

Just sad you are pushing out rxjs when it is a big reason why Angular is so good. Please at least offer rxjs apis alongside the signal ones.

[@Angular]

We are maintaining support for RxJS. This announcement is about making zone.js optional. But keep in mind that we did not announce a deprecation, we announced support for optional zones. Hope that helps!

[@tombalabomba03]

Signals are soo much better than rxjs, I cannot see why anyone would use it when they have the option to use signals

[@alexander.thalhammer]

@@tombalabomba03 There are still a lot of reasons to use RxJS. It's useful for eventing and it's far more powerful concerning it's operators. Signals are good for state and a more lightweighted solution.

[@tristanmorris5646]

Rxjs can easily solve some problems that aren't very practical to solve with signals. For now, signals and rxjs go hand in hand.

[@tarquin161234]

@@tombalabomba03 Maybe signals are good for some simple components, but if you have any complexity involving asynchronous logic, RxJS is required, and makes signals inferior.