More reasons for eschewing Java

Consider the following table:

The following is a diagram that compares the Java and Go technology stacks from a high level: 

The Java/JVM alternative has a much bigger footprint; The JVM does more (some of which your application will use) and requires more RAM. Furthermore, since there is more raw source code to the Java/JVM solution than Go, that means that there is a larger attack surface for hackers to attack. Performance? It takes time for the JIT compiler to convert your application's source code to executable binary code than Go, which is natively compiled.

Go is smaller and simpler. Java was created for profit and has been aggressively marketed. Go is not marketed. There is a streamlined process for proposing changes to the Go language. See "How to Propose Changes To Go" in the Appendix. (I have found no such process for proposing changes to Java or the JVM, but I can only image that there would be much more time and effort involved).

Given the preceding comparisons of Go v. Java it seems to boil down to Simplicity v. Complexity. Gophers tend to prefer simplicity.

"Less is exponentially more."

- Rob Pike