signals > RjJS. In a small number of cases, RxJS will prove to be a better solution. 3 function (signals, computed, effect) almost completely cover the entire functionality of RxJS which is much more complicated with dozens of functions. New project = signals rn.
You are comparing two different things. Both rxjs and signals can be used effectively for similar purposes and they can even work together as you can convert signals into observables. However, deciding on what to use depends on your use case. For some things signals can perform better while also requiring less code, for others it may be better to use rxjs straight away rather than going through several hoops.
Bro that's great! Keep going please
The explanation is so clear and helpful. Please keep it up!
The best Tus in RxJS
What in api.service.ts?
8:59
5:19
signals > RjJS. In a small number of cases, RxJS will prove to be a better solution. 3 function (signals, computed, effect) almost completely cover the entire functionality of RxJS which is much more complicated with dozens of functions. New project = signals rn.
You are comparing two different things. Both rxjs and signals can be used effectively for similar purposes and they can even work together as you can convert signals into observables. However, deciding on what to use depends on your use case. For some things signals can perform better while also requiring less code, for others it may be better to use rxjs straight away rather than going through several hoops.
when I hear your voice I feel I'm in 😴