Your Brain 🧠 on Swift Concurrency - iOS Conf SG 2023

Speaker: Donny Wals
This talk will cover some interesting bits and details about how Swift Concurrency requires a bit of a different way of thinking compared to what we used before!
Recorded by Kale ( ‪@kalestarler‬ ) and Tim Shim ( timshim)
iosconf.sg
Find us @iOSConfSG on Twitter

[@ajmarquez]

Great talk!

[@muncho404]

Phenomenal talk🤩

[@user-qg8nc5bk4p]

I was going through modern concurrency for a while and only this talk put the light on the things I didn’t quiet understand. Thanks Donny!

[@thomasminshull3456]

Really great talk. I can’t help but feel that async await isn’t production ready. There doesn’t seem to be a great way to serialize work and there seems there are a lot of “gotchas”. It makes async code easy to right and hard to reason about which is a bad combination. I feel for new developers trying to wrap their heads around this. I’m sure it will improve, it solves some interesting performance problems, and it never seems to be solving the problem you think it is.

[@dmitriyobidin6049]

As a newbie ios dev i still can't decide whether this new approach is easier or harder to compehend.

[@dangotang8918]

Apple / Swift community should pay attention to comments like this!

[@venugopalreddy6618]

I guess GCD does the job for most the cases.

[@brunolopesdemello7040]

You can use both, but with async/await you have far less code, but the impact from both are just the same

[@vaibhavbansod9111]

Cycle does the job of taking from one place to another, so why to use bikes and cars

[@dmitriyobidin6049]

So we just swap all our classes for actors or what?

[@griffinbaker860]

If it interacts with the UI, then yeah

[@dangotang8918]

@@griffinbaker860 no. actors don't have inheritance, so they can't be a stand-in for classes. actors are for when you need to encapsulate mutable state in a thread safe manner.