They seem to be aware: ", but it has memory and data race safety, OS threads, and futures, so no problem." However, futures are certainly not boilerplate-free.

They seem to be aware: ", but it has memory and data race safety, OS threads, and futures, so no problem." However, futures are certainly not boilerplate-free. They destroy your ability to use native control flow the way you can with threads (M:N or 1:1). You can get some of that back with async/await, but Rust doesn't have that and it's still not boilerplate-free.