What got me here was a sincere answer
Apr. 2nd, 2019 02:25 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
aclassifierWhat got me to Dreamwidth.org today was this thread: I wonder, why Graydon Hoare, the author of Rust, stopped contributing into it and switched to Swift? with the sincere answer by Graydon Hoare (graydon2), extract here:
I have myself been trying to follow Swift's concurrency/threading debate from this blog note: Swift-concurrency(?) (*). This is a quite interesting theme, also for me at the moment, when I was reading a student paper on Rust.
* Dislaimer: no money, no gifts, no ads and no deals etc. on any of my blog posts. Only fun and expenses!-)
Coroutines, async/await, "user-visible" asynchronicity
It's in vogue at the moment for new languages to have something like async/await. This does not mean it's a done deal: lots has been done, but lots is still messy. The boundary between synchronous-world and asynchronous world -- in terms of types, control flow, correctness, errors, modularity, composition -- is still very awkward. Whether and how to mitigate between different synchronicity regimes, especially across FFIs or differing runtimes, is hard. Integration with effects is hard. Integration with parallelism is hard. Which parts need to be supported by the language and which parts surface to the user is hard. Cognitive load is still very high. (From https://graydon2.dreamwidth.org/253769.html)
I have myself been trying to follow Swift's concurrency/threading debate from this blog note: Swift-concurrency(?) (*). This is a quite interesting theme, also for me at the moment, when I was reading a student paper on Rust.
* Dislaimer: no money, no gifts, no ads and no deals etc. on any of my blog posts. Only fun and expenses!-)
