| > Do you have a source for that claim? Genuinely curious. Hmm, no real source for the claim, just a general interest in the two VMs. JVM for work and V8 partially for work. AFAIK, those are two of the VMs that are getting the highest amount of research in due to how they are positioned. If you want more general information on V8, I suggest reading about the turbofan design docs [1]. The JVM first started doing a lot of these optimizations with Hotspot. Google poached the engineers that did Hotspot and put them to work on V8. That's why the two VMs tend to share similar optimizations. > I’ve grown more and more convinced that managed languages are the right move for most code. I tend to agree, to an extent. The JVM is very fast, but it's also memory hungry and doesn't give up the memory it claims easily. That's due to the nature of the GC algorithms it employs and some historical constraints which bloat object size. One thing you get out of non-gced languages is much lower memory usage and much better live memory density (when done correctly). [1] https://docs.google.com/presentation/d/1sOEF4MlF7LeO7uq-uThJ... |