Doesn't this preclude the easy use of goroutines to handle concurrent requests while still keeping the promised performance benefits? And since Go doesn't have

Doesn't this preclude the easy use of goroutines to handle concurrent requests while still keeping the promised performance benefits? And since Go doesn't have any infrastructure in the language to help developers deal with event loops (Futures, async/await, etc), wouldn't it be a better choice to use a language built for event loops like Rust? The use of event loops- "reactors" in Go, while proclaiming the benefits of green threading seems similar to the use of interface{} and manual code generation scripts while proclaiming the benefits of no generics or macros.