+Erlang, +Pony, +Clojure (also STM waves hello), +Haskell<p>I also found that reference highly dubious.<p>I mean the reasons Rust abandoned it were quite legitimate.  As a systems language with originally segmented stacks that performed poorly and were thus removed, which mitigated anything resembling the &quot;lightweight&quot; promise of lightweight-tasks, and then combined with the overhead of having to maintain two distinctly different IO interaction interfaces due to a lack of unification between the standard runtime and the libuv based M:N scheduler... I mean of course Rust needed to punt that semantic out of the core runtime and move it to a domain where that kind of functionality could be implemented as a library&#x2F;framework instead.  Otherwise writing consistent IO libraries for Rust would be a massive pain in the ass.<p>The point of Rust isn&#x27;t to be an opinionated framework that provides a set of prescriptive models for solving problems like Erlang&#x2F;OTP does.  The point is to be a generic systems language that you could use to build a new Erlang&#x2F;OTP shaped thing with.<p>I realize I&#x27;m quite literally preaching to the head of the International Choir Association right now though. ;-)