11–20 of 46 posts
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.
"It's not an easy problem taking the best of each, figuring out what the long-term convergence plan is." 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, becaus…
I doubt it was the developers who are responsible for the merging who came up with an 18 month estimate. Invariably it's not going to happen on time or if the 18 month milestone is hit, it'll stay alpha for quite some time. JDK7 + merging of 2 distinct VMs? Sheesh...
Sigh. 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.
Earlier quoted context omitted.
I doubt it was the developers who are responsible for the merging who came up with an 18 month estimate. Invariably it's not going to happen on time or if the 18 month milestone is hit, it'll stay alpha for quite some time. JDK7 + merging of 2 distinct VMs? Sheesh...
Oracle certainly has money to throw at the problem. The question whether the problem is one that can be solved by throwing lots of money at it will be answered in 18 months.
Sigh. 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.
> 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.
Anyone knows how this would affect JRuby?
Sigh. 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.
Sigh. 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.
It's really a shame that Java has fallen under the shadow of Oracle just as alternative JVM languages were starting to get really good.