Comparing Promises, Observables and Signals
summary
Compares concrete tradeoffs: promises (native fetch with async/await and AbortController) handle one async value; observables (RxJS) handle zero‑to‑many streams and use operators like mergeMap and switchMap to flatten and cancel inner streams; signals (framework signals used by Angular and SolidJS) hold synchronous state with dependency tracking so updates push “dirty” flags and effects pull values to avoid glitches. Shows examples: room cost and clubhouse UI, the Angular resource API to convert between observables and signals, and when to use each primitive.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:04Understanding promises
- 9:40Working with observables
- 23:03Signals for reactive state
- 37:14Conclusion and comparison
related talks
26mComparing Promises, Observables, and Signals
34mObservables for Handling Asynchrony Elegantly
25mRxJS all things!
28mWatch out: observers are here to stay
49mManaging Async With Observables
44mWhat are Observables and why should I care?
53mRxJS Observables in Angular
30mParadigms for dealing with asynchrony