3 ms·

Saying that Rust chose async because node did is such an absurdly ignorant, incorrect statement.

• jerf 3y ago
  Rust didn't choose async because of Node. Async's massive popularity is because of Node. It existed long before then, and that's precisely part of my point. It had a bad reputation before then, and it's slowly-but-surely reacquiring it now.
  • insanitybit 3y ago
    Rust didn't choose async because it was popular. You can go ahead and read the massive, multi-year discussions on the topic if you'd like. They've been going on since before 1.0.
    • twic 3y ago
      I read them at the time. The gist was basically "it has been empirically established that async is the right way to do concurrency" - ie, it was because of Node.
      • insanitybit 3y ago
        That's nonsense
      • vacuity 3y ago
        It was more "it fits best with our needs as a systems language (overloaded term, yada yada) and we should support a robust concurrency model sooner rather than later". The Rust devs were aware of green threads and the like. It is deeply unfortunate that async is still such a mess, though.
      • iopq 3y ago
        They specifically referred to C# and its efficient implementation