Co-signed. (Though I’m not totally sure I agree re:kubes, but that’s not really the important part.)

There are also at least 10 different teams using Prometheus/grafana at the big bank I work for.

Those go softs are usually stable and easy to install. We have yet to use a rust developed program.

Usability matters, and the much much higher learning curve as played against rust.

If they’re trade offs, why is the Go team making proposals to add genetics and result types?

Trade offs are one thing, defecencies are another.

And if you can think of a reason why hard coding multivalue return signatures would be better than a tuple type, then I’d like to hear it.

You've not really indicated how a multi-value return signature is even _different_ than a tuple type.

A tuple is a type constructor. A multi value return is not a type. It’s a semantic hard coded into the language spec. If you have tuples, you don’t have to add that special case to the language. You can also type alias a tuple, store it as a value, and just generally treat it like any other type.

And docker, to possibly a lesser extent.