3 ms·

The bummer about the JVM is that the first piece of advice you get when things are going wrong is "you're using Oracle Java, not OpenJDK, right?" There are sit

by alrs 12y ago

The bummer about the JVM is that the first piece of advice you get when things are going wrong is "you're using Oracle Java, not OpenJDK, right?" There are situations now where the JVM is unavoidable. It's an increasingly poor choice for greenfield development.

jdoliner 12y ago
Yeah it can be a big pain. Especially for companies who aren't already using the JVM and are forced in to it so they can leverage the Hadoop ecosystem. I've had some very painful experiences trying to figure out what's going wrong on my JVM that keeps dying somewhere over the course of MapReduce job and not leaving behind any log files.
necubi 12y ago
Since Java 7, Oracle Java and OpenJDK are nearly identical [0]. There's little reason to use the former instead of the latter. Previous to 7 OpenJDK had a much worse performance than the Sun/Oracle JDK, but that hasn't been true for a while now. It remains that the JVM is incredibly mature and performant, and almost any library you could want has been implemented on it. It also remains a fruitful ground for new language development, although LLVM is an increasingly popular alternative. [0] http://stackoverflow.com/questions/22358071/differences-between-oracle-jdk-and-open-jdk-and-garbage-collection http://stackoverflow.com/questions/22358071/differences-betw...
teacup50 12y ago
One of the highest performing VMs with some of the most advanced JIT and GC technology is a poor choice for greenfield development? In what universe? The issue with OpenJDK arose when open source folks "backported" the unstable Java 7 OpenJDK source drops to create OpenJDK6, which was ostensibly compatible with (but not identical to) Java 6. As of OpenJDK7/OpenJDK8, none of this hackery is required, and we're seeing convergence of the implementations.

3 ms·

The bummer about the JVM is that the first piece of advice you get when things are going wrong is "you're using Oracle Java, not OpenJDK, right?" There are sit

by alrs 12y ago

jdoliner 12y ago
Yeah it can be a big pain. Especially for companies who aren't already using the JVM and are forced in to it so they can leverage the Hadoop ecosystem. I've had some very painful experiences trying to figure out what's going wrong on my JVM that keeps dying somewhere over the course of MapReduce job and not leaving behind any log files.
necubi 12y ago
Since Java 7, Oracle Java and OpenJDK are nearly identical [0]. There's little reason to use the former instead of the latter. Previous to 7 OpenJDK had a much worse performance than the Sun/Oracle JDK, but that hasn't been true for a while now. It remains that the JVM is incredibly mature and performant, and almost any library you could want has been implemented on it. It also remains a fruitful ground for new language development, although LLVM is an increasingly popular alternative. [0] http://stackoverflow.com/questions/22358071/differences-between-oracle-jdk-and-open-jdk-and-garbage-collection http://stackoverflow.com/questions/22358071/differences-betw...
teacup50 12y ago
One of the highest performing VMs with some of the most advanced JIT and GC technology is a poor choice for greenfield development? In what universe? The issue with OpenJDK arose when open source folks "backported" the unstable Java 7 OpenJDK source drops to create OpenJDK6, which was ostensibly compatible with (but not identical to) Java 6. As of OpenJDK7/OpenJDK8, none of this hackery is required, and we're seeing convergence of the implementations.