Java designed for performance, when the VM settles down after n iterations pushes 'on par' with C++. There's also no reason to believe that C or C++ will be fa

Java designed for performance, when the VM settles down after n iterations pushes 'on par' with C++. There's also no reason to believe that C or C++ will be faster, because you have to 1) know how to write performant C++ code (not obvious) and 2) content with the Java-JNI-C barrier which is non-negligible. I don't see too many scenarios where taking a module and porting to C++ is really ever a thing frankly. Usually, it'd be for integrating already existing systems - or - for integrating things which might naturally be written in C/C++ in the first place. For something like Graal, it's one of those broad improvements wherein everyone gains, hopefully magically without having to do anything like a big improvement in V8 that just 'happens'.