The thing with Java - and by extension Scala - compared to Go is that Loom adds yet another concurrency and language mechanism - so developers have yet another thing to decide and choose from, and a risk of mixing styles together.

Whereas in Go there's only one way and that's it. pretty much. Oversimplified maybe, but my point is, 'bigger' languages offer options, and options increase overhead.

I support having simplified subsets of languages - or rules in a company, whatever - that sets standards as to which language, stdlib and library features to use. Less options reduces complexity. At the cost of code volume maybe, but code volume is not and never has been the problem - complexity is.