Why should You Care about Functional Reactive Programming
summary
Shows converting a thousand-line Angular component into a small RxJS pipeline and pure helpers, making side-effect hunting disappear and unit tests trivial. Implements a live Wikipedia search using debounceTime + distinctUntilChanged + switchMap to avoid callbacks, then maps results to titles and extracts fields with Ramda pipe so three messy map lines become reusable pure functions. Uses the async pipe to avoid manual subscribe/unsubscribe. Demonstrates the refactor works end-to-end and claims maintainability and testability improve dramatically.
AI-written summary · about
chapters (14)
- 0:00Introduction to FRP
- 2:22Problems with mutable state
- 3:49Pure functions explained
- 6:40Functional programming basics
- 7:46Reactive programming defined
- 8:29Issues with Promises
- 9:32Demo: Wikipedia search
- 11:19Functional reactive programming
- 13:30Refactoring API calls
- 16:43Simplifying data extraction
- 19:39Composing functions
- 21:11Benefits of FRP
- 22:37Async pipe in Angular
- 25:24Q&A and summary
related talks
42mConquering Time with Functional Reactive Programming
29mHow to use Functional Programming with Angular and why it’s a good idea
54mReactive Angular 2
51mReactive programming in Angular
37mReactive Programming with RxJS
32mMastering Reactive Programming with RxJS
33mStop Micromanaging State and Start Being Reactive
23mHow we’re embracing functional programming to build a large SPA
