Slashdot Mirror
Oracle's Newest Move To Undermine Android
GMGruman writes "Oracle's decision to shift focus from the Harmony Java open source project to OpenJDK seems innocuous enough — but InfoWorld's Josh Fruhlinger explains it's part of an effort to derail Google's mobile Android OS by gutting the open source project that Android has been driven by. IBM has signed on, apparently in return for getting the Java Community Process reactivated, leaving Google in a bind."
Google is full of smart people. I'm sure they saw this move - and the entire assault on mobile Java and derivatives thereof - coming long before Oracle started their anti-Android crusade. I'd be willing to bet that Google has something new 'brewing' for Android 3 that will leave this whole mess behind. You just don't get that many programmers together without a few being paranoid enough to have planned an 'escape module'.
Did this surprise anyone?
Let us all remember that ORACLE stands for "One Rich Asshole Called Larry Ellison"
This is the company that buys out someone else and does not even bother to offer the customers a migration path. Nor any form of support other than letting you fill out a bug report they close as the product is EOL.
Can someone explain why Oracle cares about the success/failure of Android? I honestly don't know.
The success of Android means a potential 'licensing fee' from every Android install. They don't care about Android per se, they just want to charge everyone to be able to use it.
Forgive the layman here, but why can't Android simply switch Java platforms as well? Open is Open, no?
Oracle is trying to claim that Dalvik, Android's virtual machine infringes on mobile java patents. Mobile java was not included when Java received it's current "open" licensing.
Sun started OpenJDK as the project from which the GPL'ed version of Java would be created.
It stands to reason, that Sun had planned to discontinue supporting Harmony when OpenJDK was formed.
Don't mean to spoil a good conspiracy...
These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
Oracle is trying to claim that Dalvik, Android's virtual machine infringes on mobile java patents. Mobile java was not included when Java received it's current "open" licensing.
And I'm sure part of the reason why Mobile Java wasn't in the "open licensing" was the carriers. That is, Sun had already extracted some money out of the carriers and met with a very nice bit of success there. Remember, before Apple's iPhone and Google's Android, JavaME was a big success in offering advanced features (that sucks compared to today's offerings). It was a big success for Sun licensing wise--something the original Java was not.
But with that money came a very, very hefty price. They had to bend over backwards to give the carriers what they wanted in order to "add value". One of those was charging developers $500+ a pop to be able to release applications for their network. Another for the developers to pay extra to access certain features (location). And another still was for companies like Verizon and Sprint to just flat out turn off certain features.
Which is why Apple didn't do JavaME (I remember being pretty bummed when they didn't)--they wanted complete control, and they would never get that with JavaME.
And Google had similar needs--but also didn't want to pay the licensing costs everyone else did.
JavaME was a money maker for Sun (unlike the standard Java VM), but the process of making money off of it made it a nightmare to deploy apps on. Development--writing code--was ok, but getting it to work on multiple headsets (nevermind multiple carriers) was a huge headache. And it was a huge headache because of all the compromises Sun made to get the carriers on board. And that nightmare (in addition to licensing costs) is why Google came up with their own VM implementation.
I used to be a big Java proponent for mobile development. I'm not anymore. But it is interesting to see how all those bad decisions (I cursed Sun weekly as I tried to wrestle another carrier or headset down) played out into what we have now.
Google didn't want to pay the money. Microsoft (via Miguel) likes to say they would have been better, but they are just as bad on the licensing (see HTC and now Motorola). Sounds to me like Google got used to their free ride on Java and balked at the idea of giving anyone a slice of their work and money on Android.
I'm not saying Ellison is not squeezing them (he definitely is), just that Google is kind of getting a bucket of cold water in their face about how the tech companies "collaborate" in new tech fields. Not "fair", but it is kind of predictable.
"Doubt your doubts and believe your beliefs." -- Switchfoot, Ode to Chin
Google collects a license fee from Java ME installs. Android isn't a Java ME implmenetation, obviously, and you can argue that Android is hindering the adoption of Java ME in the next generation smartphone world by absorbing the energies of the huge pool of Java programmers who might want to do mobile development. (You could also argue that Java ME was failing to catch on quite well on its own before Android showed up due to its own limitations.)
If you're interested in the background, here's an article I wrote about it a couple of months ago. (I'm the guy who wrote the article that got slashdotted, for what it's worth.)