Getting started with Angular Signals

[@Angular]

Watch all the Angular Sessions → goo.gle/IO23_angular_pin

[@RobinMeow-le7em]

I know they were called previously `SettableSignal` but since they are called `WriteableSignal` now (which I like more :thumbs_up: I think they should have the method `.write(value: T)`. This would make Kevlin henney also super happy to see less "sets" and "gets" in every code base.

[@clashclan4739]

The most complicated example to learn signals on the internet

[@manojht8036]

agreed

[@samwelkinuthia1550]

lmao you're right. The simple counter would have been fine

[@cananard]

The only thing I hate about angular is that I'm obliged to use it at my job...

[@user-san-chous]

Well, it was created by people who write documentation. It explains everything. Compare React or Vue docs with Angular docs.

[@stefanck]

Clearly, I was like "wtf, a cipher game really?..."

[@shaikhhar6911]

Its just like behaviourSubject but less verbose. I like it

[@flamousz]

yeah no neeed to subscribe, unsubscribe and change value with next()

[@ibrahimsoukak437]

Yeah I never understood what the point of signals is. It feels like another fancy way to solve a problem that I always had solved with Subjects, Emitters, and Observables. Honestly, I'm not sure I like the syntax either

[@shivappasagar]

loved the way you guys presented effects. Practically

[@baris7971]

the Example Application is pretty complicated. I Joind the other commentators mentioning to use simple Examples to explain the concepts of signals.

[@Ryval_OW]

Skill issue.

[@despacito2727]

@@Ryval_OW Expected response from a Widow main

[@vukkumsp]

Finally we can use effects in angular without ngrx, like we use with react redux.

[@PashaSemf]

Exactly how I imagined the people responsible for Angular!

[@musashi542]

naaah 💀

[@wobsoriano]

bro

[@jazy3091]

Turns 2/3 towards PashaSemf, in scripted excitement: "Now that is a marvellous observation!" - displays NaturalSmile_3.

[@vukkumsp]

I don't think all angular responsible people are on screen

[@sravant]

Example should be simple to understand. Not sure why you choose complex examples.

[@techwithjesus8263]

You both are here to confuse folks 😂😂. I love how Mark Techson explains this on Frontend Masters. I watched the video because of her.

[@marcialabrahantes3369]

This is their replacement for observables... got it!

[@tarquin161234]

It isn't a replacement. Signals are synchronous only. Rxjs also has loads of operators. This is why I'm sticking with rxjs.

[@dev-rachid]

Greatful ! thanks Angular Team 👍

[@markusingvarsson2146]

Loved the video! 🥳 a really awesome demo!

[@mxz2024]

so the main difference to behavioursubjects is, that you dont need the subscribe stuff and you have less sideffects like with multiple subscriptions and chaining pipes on one subject?

[@matthewcullum7551]

This was my takeaway. Behavior subjects, but without all the code gymnastics and memory leaks involved

[@arielunanue4354]

thanks @matthewcullum7551, I was wondering about the difference between BehaviorSubject and signals

[@Ernestas23]

Who ever came up with this example idea, did not want for people to fully understand the signals.

[@IsuCompare]

as i just started to work with angular again after 2-3 years of pause, i dont quite get the difference between two-way-bindings and signals as you can just pass the value and it will be shown on the UI when updated. other than that using behaviours also would do the job to track on some values, sharing with services is also possible..

[@RenanLeandroFerreira]

Can we use signals with forms? How signals will be integrated into Form Builder?

[@Gorgggg]

Nothing published yet, though you can soon use signals for 2 way data binding. Reactive forms will still need quite some time. Most likely we with some something with Angular 18.

[@starvingmusician152]

Wow really interesting!

[@IlijaIlijev]

Too complex example for simple things

[@aravindhmedia]

How this is different from BehaviourSubject ???

[@MuhammadFaisal04]

You cannot compute a BehaviorSubject.

[@LarsRyeJeppesen]

It's sync always.

[@MuhammadFaisal04]

Also, computing a new value from a BehaviorSubject is imperative, unlike signal which is reactive.

[@jediampm]

Hi, just a simplification: RxJS is an async reactivity where signals are sync reactivity.

[@hansschenker]

@@vkagklis Signals are not for the Devs , Signals are for the Compiler (CD)!

[@IbrahimKwakuDuah]

My oh mine, is this the intro video? What would the advance be like?

[@jandrorojas6714]

This example... oh my god 🤦‍♂

[@Angular]

Thanks for this feedback, we're going to make more examples in the future.

[@mohammedasim3158]

why dont you take very simple example?...

[@themudreco]

I liked it.

[@anapaulalopesaraujo3824]

Is this example really necessary?! No hate, but it is pretty difficult to understand. 😒

[@Angular]

Thanks for this feedback. We're releasing some new examples soon!

[@koolvoid]

My team decide to not update to angular 16 because Signals are still in development mode and not ready yet for production, is that true?

[@CodeShotsWithProfanis]

Angular Signals are in a Developer Preview. This means that the features are there, they are fully functional and pollished but the API might change in next versions.

[@Tobawa2601]

I mean you can still upgrade to angular 16 and your application should work just fine, because signals haven't replaced anything yet. The signals are part of the developer preview and shouldn't be used in productive environments at the moment.

[@koolvoid]

@@Tobawa2601 Yhea i know my team is retarded I ask to leave :)

[@BojanKogoj]

If you don't use them it's like they don't exist. Just update

[@LogUp-uf1th]

like the example provided, the video is equally complicated to decipher! Such examples should not be for the introduction of a concept!

[@ovidiumiu6283]

Feels like a kids video. vibes so fake

[@h0ph1p13]

Well this happens when a company has too much money so simple 5 minute screencast video gets so many editions that it turns into a material that looks like it was made for 6 year olds. :( Not to mention the overcomplicated framework.

[@RajinderYadav]

As angular developer I can finally say it is catching up to Vue in term of simplicity. RXJS, Observables and NGRX was a huge mistake.

[@developeroppa]

Yeah like I know observables and rxjs are powerful but were they really necessary in the first place?

[@jediampm]

Hi, thanks for the video. Two things: - when using stackblitz, please dont use inline template because of missing code highlighting. - in effect, please dont use var keyword to declare a internal variable. Use const in this case. Another things that dont see an answer for: - signals beside replace zone.js, will it replace also ngModel directive or banana in the box ? - What about forms, mainly template driven forms? thanks.

[@Gorgggg]

Hey there. Banana in a box will remain, though implementation will change a little. As 2 way data binding will be expressed as a writable signal (google for for signal components rfc angular github) Ng modules will remain. Though usage will most likely get less and less. There have been no stated plans to remove them. Regarding forms, nothing has been published yet. They will most likely work on that jn Angular 18.

[@mugatu2017]

We already have rxjs Subjects to multicast data

[@chaseliu5011]

have to say this is tutorial is so horrible

[@SuperCompilator]

A simpler way to explain this is to say: a signal is a useState in react and an effect is a useEffect in react 😊 Good job though (really)

[@siddharthkrishna2499]

Can use effects to emit signal values instead of calling the emit in multiple places? effect(() => { this.exampleSignalChangeEvent.emit(this.example_signal()); });

[@andreip.8321]

that document.getElementById in Angular hurts my eyes :D

[@AlanGramont]

var result = compute(() => info.max() + cringe.max())

[@bhanupratapsingh4879]

Greatful ! thanks Angular Team 👍