Reactive JavaScript at Netflix, Microsoft and the World
summary
Claim: observables make asynchronous code composable and cancellable and are already used in production. Microsoft Reactive Extensions exist since 2009 and evolve into ReactiveX and RxJS. Netflix redoes its player in 2014, standardizing on observables across seven platforms and handling ~one third of US broadband traffic which reduces callback hell and lets one-line scheduler swaps like requestAnimationFrame scheduler fixes animation CPU spikes. Slack uses RxJS for complex editor features such as live spell‑check and typeahead and retry logic simplify to a few declarative operators.
AI-written summary · about
chapters (25)
- 0:00Start
- 6:25The Netflix App is Asynchronous
- 6:53Asynchronous Nightmares
- 9:10Real-Time is Everywhere...
- 11:40Events and the Enemy of the State
- 12:33First Class Async with Promises
- 13:01Breaking the Promise...
- 15:43Design Patterns Elements of Reusable Object-Oriented Software
- 16:49Subject/Observer Pattern with the DOM
- 19:31Top-rated Movies Collection
- 20:15Mouse Drags Collection
- 21:00First-Class Asynchronous Values
- 21:14The General Theory of Reactivity
- 23:23What is Reactive Programming Anyhow?
- 25:24Functional Reactive Programming (FRP) is...
- 26:16Rx Grammar Police
- 28:22Client: Polling for Row Updates
- 29:52Implementing Spell Check in Slack
- 31:17Winning Friends And Influences Others
- 32:40Schedulers Matter!
- 34:38Async/Await with Observables...
- 36:43CSP Versus Observables
- 37:08Communicating Sequential Processes (CSP)
- 37:37imperative cat
- 37:57Why Observables...
