[Bognar]

> On top of that, most infra tooling—Grafana, Prometheus, Kubernetes, Terraform—is written in Go, so choosing Go for the backend comes with a ton of advantages over C#.

Not once have I ever had to interact with these technologies in a way that would benefit from my application using the same language. The language they are written in is irrelevant.

[whoknowsidont]

>Not once have I ever had to interact with these technologies in a way that would benefit from my application using the same language.

You haven't had to or refuse to? I've interacted with plenty of C# teams in my career and getting them to step outside the box to solve an actual technical problem in a reasonable way is _painful_ for this very reason.

They'd rather set up a meeting or hire more consultants and stonewall a project for over a year.

Most programmers can learn and pick up C# in like a day, but Windows-based developers seem to have a lot of trouble going the other way.

[mikeschinkel]

As a counterpoint, I have many times had to interact with the those technologies, and thus been able to use their source code as packages and/or learn their source code techniques which I have then used in my own Go programs.

What does that prove? it proves that no single developer's anecdotal evidence can be used to validate a broad-brushed claim like "The language they are written in is irrelevant."

[wavemode]

In Kubernetes at least you may benefit from the ability to write custom conteillers. But I agree with you that the need for this is relatively niche.

[gkedzierski]

I run a monitoring startup (StackScout) where I'm rewriting the main API from PHP to C#, but the actual agent you install on your servers (so typical systems programming) is and will stay written in Go. It's ok to not have all your tech stack in a single language.

[rednafi]

At Doordash, we regularly do it and interface with these tools to build custom solutions.