As a counter anecdote, I've worked at two large companies with monsterous Go codebases and they are totally fine to maintain. There is no justification to the claim that Java repos are "easier to maintain" by the above commenter, as we have decade-old Go codebases that doing great.
I'm just as fast/productive in Go (8 years of experience) as I am in Python (13 years of experience), but the resulting code is:
* more maintainable (enforced typing vs typehints+mypy)
* faster (compiled vs interpreted)
* consistently structured / opinionated (until recently we didn't have generics, which meant that engineers often had to do things the "boring and verbose way" instead of the "clever and concise way" which, though frustrating short-term, has proven to be much better for maintainability long-term.
There's no reason that your company can't support multiple languages. Uber has large Go monorepos, Java monorepos, Python monorepos, etc. and they all work in harmony and with different requirements.
I'm just as fast/productive in Go (8 years of experience) as I am in Python (13 years of experience), but the resulting code is:
There's no reason that your company can't support multiple languages. Uber has large Go monorepos, Java monorepos, Python monorepos, etc. and they all work in harmony and with different requirements.