Concurrency for Imposters
summary
Explains why Kotlin coroutines beat ad-hoc threads for UI responsiveness, showing coroutines compiled to a simple state machine that suspends blocking work and lets other tasks run, using the memorable coroutine octopus analogy. Recommends learning coroutines and RxJava, using ViewModel-scoped coroutines so cancellation happens automatically when a screen dies, preferring immutable state and funneling mutations through one thread or queue, and using Dispatchers.IO for network/file work; points to specific books and blog posts for the compiler and debugging details.
AI-written summary · about
chapters (13)
- 0:00Welcome and speaker intro
- 1:10Why this talk about concurrency
- 5:21Basics of Android concurrency
- 7:11Why use concurrency in Android
- 9:17Concurrency libraries overview
- 11:46Minimal coroutines example
- 13:33Coroutines and threads analogy
- 15:39How coroutines suspend tasks
- 17:03Common threading problems
- 21:11Handling long-running tasks
- 22:37Coroutines scope and context
- 25:06Resources for further learning
- 27:14Tips for learning concurrency
related talks
42mKotlin Coroutines: An Intro to Practical Use on Android
40mConcurrency made easy with Kotlin Coroutines
33mVisualising concurrency with Kotlin
38mKotlin coroutines
42mKotlin Coroutines: Beyond async/await
44mTesting Kotlin Coroutines
47mKotlin Coroutines
30mBetter asynchronous programming with Kotlin Coroutines