David Smith @Catfish_Man@mastodon.social
Public

I wrote up a little flowchart here for how I think about "is it ok to do this work on the default Swift Concurrency thread pool?": forums.swift.org/t/is-concurre

When to make something asynchronous, when to make it parallel, and how parallel to make it are all inherently tricky in extremis, but the default behavior is the default for a reason, and is appropriate in the vast majority of cases.

Is @concurrent now the standard tool for shifting expensive synchronous work off the main actor?

I think for the vast majority of iOS use-cases here people are overcomplicating things. Modern computing devices are unbelievably powerful. Have you verified that there’s actually a problem? “Just do it synchronously” works remarkably often, and “async but on the main actor” covers a surprisingly large chunk of the rest If there is a problem, have you used Instruments and related tools to profile and optimize the code? Fast is almost always superior to slow-but-async, for battery reasons among...

forums.swift.org · Swift Forums

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/Catfish_Man/statuses/115511015396590248 on your instance and quote it. (Note that quoting is not supported in Mastodon.)