Great, another one of these articles, but this time I feel more confident in my usual reply, having been working in Go exclusively for a while. > Implementing

Great, another one of these articles, but this time I feel more confident in my usual reply, having been working in Go exclusively for a while. > Implementing all of this functionality in Python may be doable with recent tools like asyncio, but the fact that Go is designed with this use case in mind makes our lives much easier. This just makes me think about Armin Ronacher's article on back pressure but, sure, whatever. > Building a cross-platform CLI is easier in Go No, it isn't. > The performance benefits of a compiled Go binary versus an interpreted language are also significant Ah, yes, because performance is such a key feature of command line interfaces, as evidenced by bash and its outstanding performance in every benchmark. > The Go ecosystem is great for infrastructure projects And the reality discussed in this point would be different if docker wasn't written in Go. Had the docker developers chose anything else, this point would apply to that hypothetical language, so it isn't an inherent advantage of Go as a language. > Go is just a pleasure to work with No, it really, really isn't, but that's not the point. This is ultimately the real reason they chose go: whoever made the original decision liked it and everything else is post-hoc rationalization. Which is fine, most of this tends to be subjective.