No, I had chosen Go for that problem. My reasoning was that most of the code I've read or written in the past 2 years has been Go, so it seemed like I should focus on using a language where I was warmest.

But in retrospect I would have preferred Java. That's my fault.

If you did, I wonder if you would regret choosing Java over Go for other reasons. I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language.

> I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language.

There is no final nirvana language. That is the awful truth of existence.

> no final nirvana language.

There isn't one...yet!

Perhaps their existing codebase is in Go and they need to use a utility. Perhaps they really like the performance of Go compared to Java. Perhaps they can't just use Java because of inertia or that no one else knows Java. Languages have warts, and wanting to remove one is not a bad idea.