RxJS destroy the state machine
summary
A team replaces a massive state machine with RxJS-driven event streams, turning DOM, media loading and real‑time messages into composable observables that eliminate callback‑hell and common memory leaks. Code uses takeUntil and debounce/buffer operators to cancel and group events, integrates promises for single values, and verifies behavior with a simulated test scheduler and marble testing. Resulting platform is smaller, easier to test, and reliably cleans up subscriptions so flows stop when expected.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:49Callback hell
- 3:54Error handling - no try-catch
- 4:32memory leaks, race conditions
- 5:24What is Reactive programming?
- 7:05The Microsoft definition
- 7:35The Stack Overflow
- 10:12Array and Events are Collections
- 12:49Streams are functional They can be Mapped
- 14:09Streams can be completed
- 16:14Streams are observables because they are observed
- 21:48Show me the code!
- 23:54What about memory leaks?
- 25:35Coming back to the first example
- 27:38A short demo about Javascript
- 29:10Testing example
- 30:58Marble Testing(Rx 5 only) you love testing with diagrams
- 32:35Debugging
- 34:03Rx revolution
related talks
26mRxJS: destroy the state machine!
35mManaging State in React Apps with RxJS
36mRxJS: A Better Way to Write Frontend Applications
45mHow to Manage Your UI State: Virtual DOM and RxJS
34mOperate Heavily Dynamic UIs with RxJS
33mStop Micromanaging State and Start Being Reactive
25mRxJS all things!
45mRxJS 5 In Modern Web Applications