It's really a pity the "synchronous" terminology took off, as if the layout of the text of the source code has any particular relationship to the efficiency of the underlying scheduling and multitasking primitives. In the end what matters for the code complexity is how the threads can interact with each other (shared memory, messages, etc) and how thoroughly those things are enforced, and the performance is about the efficiency and power of the underlying scheduler and processing. How your code looks in the editor doesn't enter into it.
Things with bad thread interaction stories and inefficient or ineffective schedulers aren't going to be the Next Big Language, no matter how cool they sound today.
The results in this article are a lot less weird or counterintuitive if you understand that.
Things with bad thread interaction stories and inefficient or ineffective schedulers aren't going to be the Next Big Language, no matter how cool they sound today.
The results in this article are a lot less weird or counterintuitive if you understand that.