zlacker

>I hope that someday, we can have a Rust-like language without async.

That exists today, it's called Rust. You don't have to use async.

>>nemoth+(OP)
Until you want to use a library that requires async. Now you do.

>>kelsey+J1
Which part of the standard library forces me to use async? Or is the complaint that you can't force other random developers to program in the way you prefer?

>>nemoth+R8
Can you try steel manning?

>>kelsey+5b
I'm not them, but I don't think there's any general-purpose programming language in existence that prevents developers from implementing async runtimes and using them in their libraries.

So yes, if your whole reasoning is "other people might use async and then I won't be able to use their code", then you'll be waiting indefinitely for the magical programming language that's both fully featured for your work and does not have any portion of the ecosystem implemented in async code.

>>kelsey+J1
> Until you want to use a library that requires async. Now you do.

Now you do... have an incentive to write your own which is not async.

>>sgbeal+ua1
That's fair. The Rust community does love a rewrite.