Fair enough. I always consider Go first, but I do differ in that I'm happy to take .Net second. Basically I agree with everything you said there, but with jus

Fair enough. I always consider Go first, but I do differ in that I'm happy to take .Net second. Basically I agree with everything you said there, but with just one amendment - the baggage in .Net was sort of reset not too many years ago with the introduction of Core, and how much you bring into your codebase/tooling is often a personal choice now (depending upon your project) rather than it being forced on you. For example a .Net API can be very clean, fast, free of cruft, and run anywhere from a single binary. A .Net MVC website less so unless you're careful (though I still prefer Razor over Go's default templating).