&gt;your apparently-perfect channels<p>I&#x27;ve never used Go, but it has some interesting concurrency ideas. So do Node and Erlang. I naively expect Rust to adopt the best ideas from each.<p>&gt;One can use channels to get all four of the conditions required for a deadlock, especially Go&#x27;s synchronous-by-default channels.<p>One can, yes. But it&#x27;s pretty easy to avoid cyclic locking patterns when each request is handled by a separate goroutine, as is idiomatic. One thread per request in Rust will drag pretty quickly.<p>Yes, the borrow checker is an impressive achievement. But is it enough for Rust to succeed? Marketing yourself as safer C++ is what Java already did (with tremendous success) 20 years ago. And the market for systems languages has only shrunk since then (my phone runs Java).<p>&gt;All the languages you mention are quite opinionated in their concurrency, imposing costs that Rust doesn&#x27;t and can&#x27;t, for its target space.<p>And yet Rust has already partially standardized channels. Finish the channels, add coroutines and you&#x27;ve implemented Go! (I&#x27;ll note there are already coroutine implementations for C and C++, which do not limit their use as systems languages).<p>&gt;(And, Go certainly doesn&#x27;t provide any guarantees at all, not even data race freedom.)<p>Which, interestingly, hasn&#x27;t hindered its ability to become a successful language! A lesson worth remembering.<p>&gt;Wrong, it&#x27;s very much on the roadmap, e.g. Alex Crichton (core team member) has been adding windows support to mio himself.<p>I mean...
<a href="https:&#x2F;&#x2F;github.com&#x2F;carllerche&#x2F;mio&#x2F;graphs&#x2F;contributors?from=2015-05-15&amp;to=2015-09-09&amp;type=a" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;carllerche&#x2F;mio&#x2F;graphs&#x2F;contributors?from=2...</a><p>Could be worse, could be better?<p>&gt;Why is this particular pet feature any more important than everyone else&#x27;s pet feature?<p>I don&#x27;t think &quot;good concurrency is a pet feature&quot; is the winning argument here.<p>&gt;I&#x27;m pretty confident that Rust can easily be much better (i.e. more performant and reliable) than both Node and Go and even Erlang.<p>Me too! But I&#x27;m not sure that&#x27;s going to happen with a single core developer on Mio and no timeline for standardization.