Comment by bananadrama

When I see "in Go", I infer:

* it's likely easy to build/package, since deep dependency trees don't occur much in practice. Alternatively, there could be a binary available on Github.

* it's going to behave similar to https://12factor.net/

* it's going to be working in 3 years time (since the language and library authors value backwards compatibility)

* I can contribute to it, and not expect it to use some obscure async/web library that makes contributions harder.

They're all important to me. I think Go is a bit uninspiring as a language, but maybe I don't need that.