Reactive Programming: A Better Way To Write Frontend Applications
summary
Claims that treating all UI data as time-varying streams simplifies frontend code, replaces tangled callbacks and subscription setup with declarative relationships, and demonstrates this by wiring up examples that actually run: a button-driven moving ball, a full login form example with API calls and progress state, and a production-scale signal graph for state management. Implements examples with rxjs, shows rxjs download counts overtaking React in registry stats, and ships libraries (signal, rx-react glue) used to connect graphs to React components.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:22What is a computer program
- 3:00Global Event Bus
- 6:08Observer Pattern
- 6:35Observer Pattern Example
- 9:05Drag and Drop
- 9:42Functional Reactive Programming
- 10:55Teaching
- 12:10Math Context
- 13:26Observables
- 19:12Real World Example
- 26:53Production Concerns
- 28:13Signal
- 33:03Signal Connect
- 38:39TypeScript
related talks
51mReactive Programming with JavaScript
35mHow Reactive Programming simplifies complicated Frontend applications
23mReactive Programming Made Simple
01h 00mReactive Programming, State Management, and Redux for the Modern Front End Dev
42mMake Your Frontend Reactive with RxJs
39mReactive Programming
27mFunctional Reactive Programming: What Does It Solve? Does It Solve Things? Let's Fi...
21mThinking Reactively: Most Difficult