Also have worked in some pretty massive Go codebases. It's about writing the language idiomatically. If you're super concerned with trying to mimic Java-style a

Also have worked in some pretty massive Go codebases. It's about writing the language idiomatically. If you're super concerned with trying to mimic Java-style abstraction and shoe-horning OOP into Go you're going to have an awful time. If anything, I've found shipping code to be WAY faster in Go than Java due to the much cleaner build system and approach to testing. The one main area where Go struggles is in math-heavy code where the lack of generics or algebraic types means duplication or code-gen. But you're right. It's not the be all end all of languages. If anything, it's just a much better substitute for the use cases where Java traditionally excels.