I do talk about that. Hotspot is just a fancy Java trademark name for Just-in-Time compilation. There are lots of ways of doing that. Hotspot is one way, and it isn't even the best way IMHO.

But the point that I was making is that this does not seem to matter much. Go still typiclal beats Java in most real world scenarious and in micro-benchmarks.

JIT compilation isn't magic. If you haven't designed your language for it, then there are limits to how far you can take it. Java e.g. was not designed for JIT compilation. They just tacked it on. That is different from something like Julia which will outpeform Java despite not being statically typed. The reason is in part because it was specifically designed to be JIT compiled.

A key problem with Java is that they missed the boat on having good language features to manage memory. Go is much better in this regard. If you have the time, you could look at a talk I had at NDC about this issue: https://www.youtube.com/watch?v=zJVtpkxq_X0