Everyday Reactive
summary
Reactive reduces explicit state by deriving outputs from streams and works well for view–viewmodel bindings and treating network calls like button-tap events; examples use RxSwift, ReactiveCocoa/ReactiveSwift, Bond and a lightweight in-house signals system used at Ustream for apps with millions of users. Debugging is harder so use log/debug operators, prefer immutability and schedulers to avoid race conditions, and be cautious injecting side effects because hot vs cold streams change behavior.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:36Ustream
- 1:30Reactive Programming
- 2:16Advantages of Reactive Programming
- 3:31Reactive Technology
- 4:02Reactive frameworks
- 5:37When to use reactive
- 7:11Observing values
- 7:22Signal
- 8:12Three flags
- 9:02Transformation
- 9:19Combining
- 10:12Reactive Streams
- 10:58Combining Streams
- 11:39Debugging
- 12:03Troubleshooting
- 12:21Debug
- 13:55Bindings
- 14:51Side Effects
- 15:56Tracking
- 16:36Saying No
- 17:09Not Always Useful
- 18:31Keep It Simple
- 19:35API
- 20:05Questions
related talks
34mEffective Reactive Architecture
41mBe ReactiveX, My Friend
24mReactive Thinking in iOS Development
01h 21mReactive Web Applications
41mThe definite guide to reactive programming in Java
01h 04mFrom Functional to Reactive Programming
45mGoing Reactive - An Introduction to Reactive Programming
48mReactive for the Impatient