Journey from procedural to reactive JavaScript with stops
summary
A concrete migration path: start with small pure functions and array helpers (lodash/ramda), move to map + forEach pipeline, add lazy operators and buffering to avoid intermediate arrays, use promises for single-shot async and event emitters for repeated async, then switch to observable streams (Rx) with flatMapLatest with promises and zipping to synchronize time and data. At KRA this reduces surprises though losing explicit return values causes the most friction; surprisingly two of three top npm dependents are underscore or lodash.
AI-written summary · about
chapters (8)
- 0:00Start
- 10:01Boring code does not surprise you
- 10:35Pure functions are boring
- 11:13Boring functions make new boring functions
- 18:17Lazy evaluation
- 19:01Lazy async eval
- 23:11Remember Array ES5 methods?
- 25:27Reactive programming
related talks
24mAdding Even More Fun to Functional Programming With RXJS
27mReactive Programming in Node
42mReactive JavaScript with RxJS
41mNext Generation Asynchronous Patterns in JavaScript
34mFunctional JavaScript for everyone
36mIntroduction to RxJS
42mBeyond Promises: Async Patterns in JavaScript
42mConquering Time with Functional Reactive Programming