In Java's case there are quite a few JVMs, many of those with AOT compilation to choose from, even implemented in Java itself.
Yes, CodenameOne, JamaicaVM, Aonix Perc and J9 all support AOT compilation besides normal JIT.
The Oracle Hotspot replacement project, Graal allows for AOT compilation via SubstrateVM.
There there is RoboVM for targeting iOS applications, with WP support getting added now.
Android is replacing Dalvik with ART, which does AOT compilation at installation time.
Probably a few more that I am not aware.
The only comparison with regards to Java was with the representation of integers, IIRC, which isn't really a native vs VM issue.
http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
What Dave's presentation mentions is the memory... note the huge difference in memory footprints of the programs. That's where java loses heavily, and that can affect speed as well, which was his point.
Does adding Generics heavy code move the needle in Java's favor?
As a Scala developer your comment just jumped out at me because even doing a lot of Akka this past week, there's hardly a line of code that doesn't instantiate or manipulate a Generic.
Just curious. I'm sure Go will get faster. I'm sure it's better suited to certain problems (memory constrained especially).
Frankly, this is just strong intellectual dishonesty.
If you're going to harp on rigor, then you need to consider then eliminate the prospect of an honest mistake.
*compared to non-native languages like Python and Java.
Could people please stop calling their favourite language fast just because it beats an interpreted/VM language.