Quick look at the language benchmark games, and Go is not 10x slower than Java for most tests. Java is often 3-5x slower than C/C++/etc (although maybe it didn't get enough time to warm up).
Well given both C and Go are native compiled languages, I would think C is a realistic (if distant) goal for Go performance, at least for algorithmic stuff where you're not bouncing in and out of the runtime. I was commenting on how far it has to go.
Ok, I see. Technically a JIT compiles to native code too, so for a long running app there shouldn't be much difference. Both Go and Java are garbage collected, but the JVM has the more sophisticated GC.
