The cleanest asynchronous io model that I have ever seen.
Simple serialization by default.
Did I mention the blazing fast compile times? Just that would make it way more “faster” to build your service in Go :)
And above all the language is simple with robust idioms.
Okay, I admit it is somewhat too simple, cough generics. And you won’t get C like performances for sure.
Generally Go code isn't written like typical multithreaded code with synchronization unless you're really trying to optimize something.
When you talking about async/await, you're actually talking about asynchronization, and when you talking about goroutine, you're talking about parallel (which is a selling point of Go).
If the thread that responsible for executing the async/await blocks, then the entire progress/thread rely on that async/await will block. So if you want to comfortably use async/await, the entire call stack must be build for it, and that can be a huge challenge for the ecosystem of that language.
goroutine resolved that problem by spawn a new system thread so the rest of the progress will not be effected too much by the block. Go also resolved that problem by wrapping IO on top of an internal async API so basic IO operation will not cause actual block for too long.
When a thread responsible for async/await needs to block, the task is parked and another one will get allocated to the running thread.
[1] https://github.com/rust-lang/rfcs/pull/2033 [2] https://github.com/alexcrichton/futures-await