Totally agree. A inbuilt story for concurrency helps to create a solid and mostly unified ecosystem around the language, especially around anything that is IO r

Totally agree. A inbuilt story for concurrency helps to create a solid and mostly unified ecosystem around the language, especially around anything that is IO related. The contrast to these are C++ systems, where nearly each application and framework has it's own eventloop integration (and/or coroutine implementations, thread models, futures, ...). This means integration between various libraries gets super hard and code reuse isn't that big. The only language I can think of which isn't super opinionated but get's now halfway standardized APIs is C#, due to the standardization on Task<T> APIs and async/await. It will get pretty interesting what the future will bring for Rust and Swift, as these are not opinionated either.