FWIW I'm think I'm a step above being a casual Swift user but I think this question still applies. Concurrency in Swift seems like an ever evolving topic. Sometimes I doubt how beneficial / valid it would be to watch WWDC 22 (for example) vids on concurrency topics because perhaps the content there is stale?. Has Apple ever set a precedent for removing WWDC content due to some radical change? It feels like I should be gravitating to the proposals in lieu of videos but sometimes it's nice to change the learning approach and consume video content. Would anyone advise against being too reliant on WWDC content in the ever changing world of Swift concurrency?
For casual users, is it safe to treat WWDC videos (at least for concurrency) as the source of truth?
Apple doesn't share why they remove videos, but they have certainly removed older WWDC videos, and it seems like it happens most often when the subject matter is out of date. WWDC videos are usually fine, even for concurrency, they'll just lack nuance as time goes on and new features are introduced, or new defaults are used.
In the future I hope that the longer form documentation proposed in another thread could be the ultimate source of truth for language features, updated by the community over time.
For concurrency at least (which is something I know about) all the videos are still relevant.
In general all the years of changes are just fleshing out the model but there have not been major changes to the underlying ideas, theyâve remained the same really â and APIs as well.
The thing worth calling out here is probably the the recent nonisolated(nonsending) by Default mode which does âflip the defaultâ of the how async functions behave (docs here), and the âMainActor isolation by defaultâ (proposal here), which again just âswitches the defaultâ if enabled. But all the concepts talked about in past videos are the same and still relevant.
This WWDC25: Embracing Swift concurrency session is talking about those modes, and how ad when to enable them, so you can start from there and work backwards if youâre missing anything from these explanations.