Thinking Reactively: Most Difficult
summary
Claim: structuring apps reactively removes whole classes of bugs. Uses RxJS subjects, async pipe in templates, and switchMap chains instead of manual subscribe. Example: a tournament app stops notifying new follows until refresh; the broken code points to a plain Subject with about 82 references and months of chasing; a proper reactive chain fixes it and prevents out‑of‑order results without extra debounced delays or cancelled requests.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:57The Problem
- 3:41My Experience
- 4:21Imperative vs Reactive
- 4:52Reactive App Structure
- 6:12Example
- 10:16Differences
- 12:50Opinions
- 18:53Summary
related talks
40mReactive Programming: A Better Way To Write Frontend Applications
26mReactive Programming Future Proof Your Code
31m(React)ive State Management: Enter RxJS
28mReactive Programming Demystified Drink the Kool-Aid
36mRxJS: A Better Way to Write Frontend Applications
28mReacting to change
34mEffective Reactive Architecture
23mHow we’re embracing functional programming to build a large SPA