3 ms·
So, do you mean Java or the JVM? Because here we're talking about the JVM; that means Java, Clojure, Groovy, JRuby, Scala etc. Sometimes the JVM isn't the righ
by pron 14y ago
So, do you mean Java or the JVM? Because here we're talking about the JVM; that means Java, Clojure, Groovy, JRuby, Scala etc.
Sometimes the JVM isn't the right tool; Java the language is often the wrong tool. But when you need to write large, high-performance, backend software, the JVM is pretty much the only rational choice. C/C++ is too expensive effort-wise, in development, in maintenance and in monitoring. Erlang is awesome, but it's too slow for some things. .Net is not robust on non-windows platforms (I'm not sure about this, but this is the common perception). Go is slower than Java, lacks the huge ecosystem, and also doesn't provide all the JVM goodies like runtime instrumentation and profiling, hot code swapping, good monitoring etc. Rust is too immature (and won't give you those benefits either). So, pretty often, the JVM is the only choice and you think it's time to kill it?