I&#x27;m with you on the last bit, honestly. There is room for some statically-typed language to occupy the network-services niche where performance needs to be good—maybe 2x slower than optimal (note that this is not acceptable for all network services)—and speed of development trumps most other considerations. Some sort of hybrid of Swift, Rust, and Go, perhaps, as none of them are 100% ideal for this space.<p>It&#x27;s no secret at this point that I disagree with lots of Go&#x27;s language design decisions, but it&#x27;s undeniably an excellent <i>tool</i>, whatever its strengths or weaknesses as a <i>language</i> are (hat tip to tptacek for this phrase). The Go team and community did a great job of making it very practical.