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.
I fail to see how Go being slower than Java relates to C being faster than Java.