Комментарии:
We already have rxjs Subjects to multicast data
ОтветитьHow this is different from BehaviourSubject ???
Ответить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.
Can use effects to emit signal values instead of calling the emit in multiple places?
effect(() => {
this.exampleSignalChangeEvent.emit(this.example_signal());
});
Feels like a kids video. vibes so fake
Ответить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?
ОтветитьThe most complicated example to learn signals on the internet
ОтветитьExample should be simple to understand.
Not sure why you choose complex examples.
Too complex example for simple things
ОтветитьGreatful !
thanks Angular Team 👍
Loved the video! 🥳 a really awesome demo!
Ответитьthe Example Application is pretty complicated. I Joind the other commentators mentioning to use simple Examples to explain the concepts of signals.
ОтветитьSeems like ideas are derived from AngularJS $watch, $emit, $broadcast, $on
Ответитьthat document.getElementById in Angular hurts my eyes :D
ОтветитьWow really interesting!
ОтветитьCan we use signals with forms? How signals will be integrated into Form Builder?
ОтветитьI liked it.
ОтветитьExactly how I imagined the people responsible for Angular!
Ответитьlike the example provided, the video is equally complicated to decipher! Such examples should not be for the introduction of a concept!
Ответить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)
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.
Ответить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?
ОтветитьThis example... oh my god 🤦♂
Ответитьwhy dont you take very simple example?...
ОтветитьMy oh mine, is this the intro video? What would the advance be like?
ОтветитьIs this example really necessary?! No hate, but it is pretty difficult to understand. 😒
Ответитьvar result = compute(() => info.max() + cringe.max())
Ответитьhave to say this is tutorial is so horrible
ОтветитьGreatful !
thanks Angular Team 👍
This is their replacement for observables... got it!
ОтветитьIts just like behaviourSubject but less verbose. I like it
Ответить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..
ОтветитьWho ever came up with this example idea, did not want for people to fully understand the signals.
ОтветитьYou both are here to confuse folks 😂😂. I love how Mark Techson explains this on Frontend Masters. I watched the video because of her.
ОтветитьFinally we can use effects in angular without ngrx, like we use with react redux.
Ответитьloved the way you guys presented effects. Practically
Ответить