12 years after legal action to stop Microsoft’s development of their own Java version, they offer hosted Java support

I find this somewhat hard to believe. 12 years ago, legal action by Sun Microsystems against Microsoft halted Microsoft’s development of their own flavor of Java, which was only partially compatible with Sun’s Test Computability Kit (TCK). In order to develop an implementation of Java and compatible JVM, the license requires the developed product to pass the TCK in order to maintain cross platform compatibility of different implementations of Java.

This week Microsoft announced that it has added support to host Oracle Weblogic and Oracle databases on it’s Azure cloud, allowing developers to host Java based solutions on Microsoft’s hosted platform.

How times have changed 🙂

Java 8 will ship without Project Jigsaw, modular dependencies for the Java platform

Around this time two years ago, Oracle gave the Java community two options for the upcoming Java 7 release, Plan A and Plan B, which looked something like this:

Plan A: JDK 7 (as currently defined) Mid 2012
Plan B: JDK 7 (minus Lambda, Jigsaw, and part of Coin) Mid 2011
        JDK 8 (Lambda, Jigsaw, the rest of Coin, ++) Late 2012

Oracle went with Plan B based on community feedback, and we got Java 7 earlier, just with a reduced list of changes.

Now we’re on the verge of seeing the release of Java 8, Oracle has some rather upsetting news that the major changes, namely Project Jigsaw (to introduce modular dependencies into the Java platform), will not be included in Java 8 after all.

I don’t want to see any product released before it’s ready, there’s no point shipping something if its half-baked. But with the Plan A/Plan B approach it seems somehow that we’ve been short-changed. We agreed to delay significant changes to a future release just to keep the new releases coming, and now we’re at the point where we should have received the most significant platform changes that were originally planned for Java 7, to be included in Java 8, and Oracle is telling us ‘sorry, they’re not ready’.  At this point one has to wonder where Oracle’s priorities are with Java, because it’s certainly not looking very promising right now.