1) It ignores where Java is being used. It is dominant within the enterprise. Features like a single binary, lack of a reverse proxy or taking advantage of multiple cores aren't at all compelling. We have dedicated ops teams happy to automate deployments, hardware load balancers and are rarely doing anything CPU intensive.
2) It ignores language trends. Functional programming is what is hot right with Scala and Clojure being what most enterprises are choosing to adopt for the next big project. Why ? Because they can leverage all their existing Java libraries/practices but without the boilerplate and language overhead of Java.
3) It ignores architectural trends. Go's concurrency approaches are nice but aren't that special and again aren't that useful in most cases. Unless you are someone like Cloudflare it is far easier to just horizontally scale your app servers across seperate instances. It's more expensive but hardly worth deciding your platform over.