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