I'm suspecting (but can't back it up with empirics until I get a large team using golang), that because of the advance in popularity of golang and huge increase

I'm suspecting (but can't back it up with empirics until I get a large team using golang), that because of the advance in popularity of golang and huge increase of golang codebases, the choice of golang is just as much a business decision as it is a programmer decision. If golang does prove to be a "get shit done" language, your VP is not going to be as concerned about what devs think if it can be used to get to market faster. Doesn't make any diff if it is goog or a 3 person shop. I can give you some counter-testimonial for .net when I ran a 50 dev project. Skillsets were all over the place, the architects wrote boilerplate the devs didn't understand, and the codebase was messy, thanks in due part to .net drawing commodity developers and Anders making sure csharp has 5 different ways to do everything. Lang history driven in large part by new features is turning out to be bad for business, IMO. I want something solid for my team that's easy to code, easy to test, and easy to consistently hire for. And I want them all to be SME's on the code they write for their domain. What that gets me is a lot of devs who will effort point stories about the same, no matter what team they are on. My gut tells me I can get to that state of bliss with something like golang faster than I can .net. Lot of mitigating factors built into that I get it, but that's what my gut tells me.