Oracle set to merge Java virtual machines
networkworld.com
networkworld.com
Step 1: Write a (proprietary) hybrid VM merging Hotspot and JRockit with lots of difficult-to-implement, succulent features.
Step 2: Modify the JDK 7 spec to include these features.
Step 3: Wag tail as OpenJDK slips into obsolescence.
We can simply remove all references to Oracle trademarks from the OpenJDK and continue with it. It may be unable to run software that targets Oracle's evil VM, but it will happily run whatever is built for it.
It's a shame, but it could work.
If you fork it, then you're in essence splitting these user bases, to the great detriment of both.
What is the oldest JVM Clojure can run on? Many "big enterprises" run technology that's years behind the latest and greatest. And I have been waiting for 1.7 since the time I actually wrote Java code.
I doubt the JIT part is accessible to many developers - and those who want to adapt the JIT (= mobile hardware vendors, at this stage) could always strike a licensing deal with Oracle. There are already plenty of interpreted VM implementations, so it's not the general lack of a VM either. Sun's JVM was always freely available and downloadable, even though it sometimes contains Yahoo Toolbar.
I'm sure they'll always provide a free version for desktop users, in the interests of having a wide install base. But given the pricing schemes for other Oracle products, I fully expect you'd start seeing things like per-CPU licensing for enterprises, and developer licences for the JDK.
Unless something happens, I'd be VERY surprised if the "standard" JVM is still "free to use", let alone open source, in 5 years.
And will probably kill Java in the process.
Java Enterprise is alive and healthy, thank you very much. No reason to believe that it will not continue to do pretty good for the next decade at least.
All of this happened before, and it will happen again.
Or relevant
Here's to hoping it happens in a constructive way rather than becoming so fragmented it's no good.
I hate to say it but a lot seems to depend on the ability of Oracle to make the smart move here.
That's an understatement. The complexity of merging two fairly distinct VMs while trying to maintain feature parity with both separate previous versions, and taking the best features of both? Eighteen months seems optimistic. I also hope they have some incredibly good way of producing a combined test suite, because this seems like the most promising way of introducing myriad subtle bugs I can imagine.
If there is insanely great stuff in the intersection you mention, it probably constitutes a research project, which it would make sense to undertake in the background (if at all). For Oracle, the only "insanely great" that counts is that which yields benefits that customers will pay for now/soon - not what's technically impressive. They're a sort of microsoft-research anti-particle. disclaimer I actually have no idea.
As Oracle makes it harder and harder to use the JVM people are forced into the waiting arms of MSFT
They know that the open source community won't be able to seriously fork Java/OpenJDK. Even with newer JVM languages, Java's place has been cemented in enterprise environments. And if it is one thing Oracle knows, it is how to sell to the enterprise.
I'm not sure that I would do much differently if I were them either. Open source just doesn't seem to be in their DNA, and it's been quite successful for them. Even if it is to the detriment of others...
(Hotspot+JRockit)-Zombie = Enterprise JDK with paywall
OpenJDK = Free JDK without the fun/fast/secure/... stuff
However, this would open the door for them to do evil things like, for example, charging money for the JDK.