Most of these answers don't seem to be written by anyone actually involved in "enterprise" development. Here are our simple reasons: * The JVM is fast. * The JVM can take proper advantage of multiple cores directly (no GIL). * The JVM is efficient compared to other runtimes. * Java is type-safe. * There's a library for everything , and libraries are generally well-documented, unit-tested, and provide stable releases…
Nah. Those are the reasons that an organization would like to list for using Java. But "kls" nailed it above. It's mainly inertia and labor availability at this point. The reality is that most enterprise projects are generally so many layers of lasagna code that JVM performance is about 20 down on the list of things to blame for poor performance.
Perhaps, but you can't ignore the reasons that the inertia and labor pool came to be in the first place, many of which nupark2 lists and which are still valid.