Do We Really Need Swift Modern Concurrency?
summary
The talk explains Swift’s modern concurrency model introduced in Swift 5.5 — specifically Task, async/await, and actors — and why these are more than just new syntax compared to traditional queues and threads. It covers the historical roots of the model (dating back to ideas from the 1960s), how Swift implements and uses these mechanisms, and argues for migrating existing and new projects to this concurrency approach.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:32Why Modern Concurrency matters
- 3:14What is Swift Modern Concurrency
- 10:02Coroutines: history and definitions
- 17:09Threads vs coroutines
- 20:00Swift Concurrency Manifesto
- 22:53Apple’s naming choice
- 23:55How Tasks work in Swift
- 26:01Structured vs unstructured concurrency
- 27:25Pros of Swift coroutines
- 29:56Cons and challenges
- 31:24Should you adopt Modern Concurrency
- 34:11Behind the scenes
- 35:16Resources and materials
- 36:56Q&A
related talks
47mDo We Really Need Actors in Swift Concurrency?
23mSwift Concurrency is new and hard, and you can do it
30mA Practical Guide to Swift Concurrency
31mFuture of Swift: A Sneak Peek at async / await
31mYour Brain 🧠 on Swift Concurrency
26mSwift Concurrency Under the Hood
35mThe Multi-Threaded Asynchronous Parallel World of Swift
45mThreads, Queues, and Things to Come: Present and Future of Concurrency in Swift