[soggybutter]

Java has a bad reputation for being bloated and/or slow. I find Java and Go to be fairly similar (both GC'd, both fairly high performance, both statically typed), and yet Go has a reputation for being compact and fast.

Java isn't particularly fun or thrilling to write. If you're a founding CTO or a founding team of engineers, of course you're going to choose something more "interesting" for a greenfield project.

Java isn't as quick and dirty as other languages. I think this almost fully explains the prevalence of node, because after being stuck in the node ecosystem for two years, I truly can't imagine why anyone would choose to build anything substantial in node.

[kaba0]

The funny thing is that Go is more verbose than Java, while this is never mocked in Go.

[alphabettsy]

More verbose but easier to read and reason about in my opinion. A trade-off I’ll happily make.

[kaba0]

I don’t know, Java is a more expressive language which allows for more abstractions. This can be abused, but I think Java does strike a good balance here. You can express something like the Stream API (which is imo much more readable than deeply nested loops), while most of your code will still be ordinary method calls on objects. There certainly is an enterprise style of Java, but that is not inherent in the language, and modern Java really tries to grow away from it.