Understanding the principles of Rx, Flow, Compose, and more, through Programming Paradigms
summary
Argues that RxJava, Kotlin Flow and Compose share core ideas but differ by paradigm, builds from silicon to machine code to show a declarativeness gradient and why discrete time streams are the right model for reactive libraries, contrasts discrete synchronous = reactive with continuous FRP and coroutines, demonstrates common bugs (calling getValue vs fromCallable), shows small listener→Rx bridges and recommends keeping side effects in subscribe and preferring a single Rx stream for determinism to reduce accidental nondeterminism.
AI-written summary · about
chapters (12)
- 0:00Introduction and talk overview
- 1:14Programming paradigms overview
- 4:01From silicon to programming
- 10:03Layers of abstraction in programming
- 11:27Imperative vs declarative programming
- 13:57Object-oriented programming paradigms
- 16:03Programming paradigms features
- 17:48Concurrency paradigms explained
- 23:51Misusing reactive patterns
- 28:04Strong abstractions and paradigm rules
- 30:36Future of programming paradigms
- 31:22Summary and key takeaways
related talks
53mGetting into the Flow: building applications with Reactive Streams
01h 04mFrom Functional to Reactive Programming
36mRx in Multiplatformland
41mThe definite guide to reactive programming in Java
56mThirst-quenching Streams for the Reactive Mind
43mReactive Programming in Java
44mThirst-Quenching Streams for the Reactive Mind
52mReactive Programming in Java
