✳flâneur — a map of the web's best reading

Swift Concurrency Waits for No One

saagarjha.com · 3,396 words · saved by 1 readers

There was once a master engineer who lived by herself in a mystical, far off place, where nourishment flowed freely and the dirt beneath your feet was more valuable than gold. Inaccessible even by foot, only very few could make the trip for a chance at receiving her wisdom. A novice programmer, enthusiastic but still wet behind the ears, visited her one day. “I have read your code,” he began, “and I can only describe it as sublime. But, I’ve been learning a lot about Swift Concurrency and I see that you don’t use it all the time. Why is that?” The master engineer replied promptly with a question of her own: “Tell me, how would an asynchronous program call synchronous code?” “That’s easy,” he replied. “You can just call it directly.” “Now, how would one invoke asynchronous code from a synchronous context?” “Spawn a Task, obviously!” replied the novice engineer, glad that his studies had come in handy. The master engineer smiled. “Very good. But now, imagine waiting for the work to compl

There was once a master engineer who lived by herself in a mystical, far off place, where nourishment flowed freely and the dirt beneath your feet was more valuable than gold. Inaccessible even by foot, only very few could make the trip for a chance at receiving her wisdom. A novice programmer, enthusiastic but still wet behind the ears, visited her one day. “I have read your code,” he began, “and I can only describe it as sublime. But, I’ve been learning a lot about Swift Concurrency and I see that you don’t use it all the time. Why is that?” The master engineer replied promptly with a questi

Explore this link on the map →

saved by

related reading