If you look at rust now, I think it's a great example of keeping the _spirit_ but allowing to question just about any specific decision.
Funny that the "why not go" still stands, minus the "no generics" part.
On a different timeline, Rust reaching 1.0 before Go, I bet Docker and Kubernetes would have pivoted from Python/Java into Rust instead of Go.
Given its more ambitious goals and greater scope, Rust was always going to take a lot longer to mature than Go, so that there was no plausible chance of it reaching 1.0 before Go, if they started within a year or two of each other.
I wonder, aren't there specific attributes of the Go language that makes it a particularly good fit for things like Docker/Kubernetes?
Easy to learn language and don't have to worry that much about memory, seen as a modern replacement of C in userspace, coroutines are easy to use and suit the lifecycle of network applications.