It&#x27;s incorrect to say that Rust hasn&#x27;t prioritized higher-level concurrency tools. Many of the design decisions over the previous years have been made with an eye towards supporting every concurrency paradigm.<p>For example, here&#x27;s a post of Niko Matsakis&#x27; from Feb 2014 about changing a fundamental aspect of the borrow checker in order to better support data parallelism in the future: <a href="http:&#x2F;&#x2F;smallcultfollowing.com&#x2F;babysteps&#x2F;blog&#x2F;2014&#x2F;02&#x2F;25&#x2F;rust-rfc-stronger-guarantees-for-mutable-borrows&#x2F;" rel="nofollow">http:&#x2F;&#x2F;smallcultfollowing.com&#x2F;babysteps&#x2F;blog&#x2F;2014&#x2F;02&#x2F;25&#x2F;rust...</a><p>For another example, here&#x27;s an RFC from Nov 2014 about fundamentally altering Rust&#x27;s concurrency support in order to better support fork-join parallelism in the future: <a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;blob&#x2F;master&#x2F;text&#x2F;0458-send-improvements.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;rfcs&#x2F;blob&#x2F;master&#x2F;text&#x2F;0458-send...</a><p>I&#x27;m also confused about your perception that the rhetoric gets ahead of the language. The type system does indeed make things easier and safer. When people ask what that means, we&#x27;re eager to elaborate on the precise guarantees that Rust provides. Misleading people as to Rust&#x27;s capabilities is not on the agenda.