I think you've misdiagnosed things here. Large Java codebases in giant companies are often very poor because: 1. Giant non-software companies often have low h

I think you've misdiagnosed things here. Large Java codebases in giant companies are often very poor because: 1. Giant non-software companies often have low hiring bars for their software teams. 2. They are full of bored programmers working on boring software, these people then find ways to make their lives more interesting and kill the time by over-engineering things. 3. These codebases are often very large, old, and have suffered many requirements changes with little or no time allocated to clearing technical debt. There's nothing in Go that'd make any of these things better. It may superficially appear this way because Go is, in the grand scheme of things, still quite new and hardly used in the enterprise (because it doesn't solve anything better than Java), and as such there aren't any large enterprise codebases written in it. But if you compare the language features, it's hard to explain what would make Go result in better quality software than Java and easy to find things that'd make it worse.