jvms

Anyway, the issue with JVMs is that they don't have predictable performance, not that the compilers can't be ported.

About the Batik library: What makes you think that it is the JVMs fault that it uses that much memory?

Dynamic linking everywhere has been one of the JVMs greatest strengths and best selling points.

But you can't make money selling JVMs; the Sun licensing fees and the large team required for conformance testing soak up any margins.

This meant the JVMs could really evolve unlike the Python and Ruby ones.

Java has plenty of GCs from several certified JVMs to choose from.

Almost all commercial JVMs do support AOT compilation.

Most commercial JVMs do have native compilation,.

You could, I suppose, hack something together using multiple JVMs per machine (avoid global GC) and Akka and implement some custom live diagnostics, but if you're really doing a telecommunications project there's no real shortcut.

Those organizations you've mentioned probably do take advantage of bytecode manipulation (they have undoubtedly used shadowing, and probably some agents) even though they don't write manipulation -- or hot-swapping -- code themselves, and they certainly enjoy the JVMs unmatched monitoring.

> Go has the undisputed upper hand when it comes to command-line apps Only because most developers don't care to look for the JVMs that offer AOT or refuse to use anything other than the OpenJDK.