You mean the Google legal shenanigans that tried to find loopholes around two Java licenses (one of them completely open-source, and the other would have cost them $25M) that would hopefully hold up in a court case (which they were sure would follow, because they went straight after Sun's business), failed, and in the process forked the ecosystem?
Oracle did exactly what Google dared them to do (after a reprieve while Sun was dying). Only, to get what they wanted -- payment for the use of Java not under its open-source license -- they used whatever legal argument they could come up with, in the hope that one would stick. One did (well, at least partially), and now Oracle is at fault? This entire court case -- except the decision -- was orchestrated by Google. They could have avoided the whole thing by either abiding by the open-source license (which, BTW, is exactly the same as Linux's) or by paying Sun $25M. Oracle, OTOH, had no choice because Google went after them with their own weapon.
Oracle didn't just go after someone who'd forked Java. They went after someone who'd forked Java with the intent to harm on of their main income sources from Java (at least at the time), while forking the ecosystem and breaking compatibility -- the ecosystem's prime directive -- and all that while Java was available under an open-source license, which Google rejected. They don't care about the principles of copyright. They just happened to use that in their arsenal of legal tools to go after a company that they believed had harmed them.
Then, Google's PR tried to terrify the world with the possible repercussions of the one argument that did stick by blowing it out of proportion and neglecting to mention that it hardly applies to any software these days.
Neither of these companies is a saint in this story. They are just two corporations playing their parts. But Google was the one who could have stopped all this, and blaming the whole thing on Oracle is just ridiculous.
Of course, that's not true, and you know it's not true, since you replied earlier this year to someone who explained that the alleged offer was $20M + 10% of Android's revenue (capped at $25M) for a three year license - and this was in 2006, years before Android had even launched. FSM knows what Oracle would have demanded after Android was a proven success and Google had caved earlier.
Of course, one may still think Google should have paid whatever Sun/Oracle asked for, but let's not spread misinformation.
-- James Gosling, http://nighthacks.com/roller/jag/entry/my_attitude_on_oracle...
If you check his blog he has another posts about the whole issue.
So, what do you think the SSO of 37 Java API's are worth?
Also, since all Oracle has left is the SSO claim of 37 Java API's, what do you think that's worth? And do you really support the copyright of API SSO?
WRONG! OpenJDK is 100% open source with absolutely no restrictions whatsoever[1]. Restrictions apply to other Java licensing methods, some of them may also be free as in beer but not as in speech.
> And do you really support the copyright of API SSO?
I think there are valid arguments either way (e.g., a book's TOC is copyrighted), but the use of an API for implementing a compatible version should be allowed regardless of the copyrightability issue.
But whatever your opinion is, blaming Oracle for this is hypocritical. Their goal wasn't to copyright their APIs. Their goal was to get Google to pay for Android, and they used whatever tool they could think of in their legal arsenal. Any other company would have done the same. And keep in mind -- they didn't do it on principle. Google directly attacked one of their major revenue streams -- licensing (under a non-GPL license) of Java for mobile devices. What Google did was highly unusual. I'm unaware of any such event in the past two decades or maybe even ever. It was Google who provoked Sun to sue them, and now they're trying to gain sympathy by crying over the weapon that happened to hit. But they knew Sun (or Oracle) would come after them, they started this, and now they want people to blame Oracle for any collateral damage.
The collateral damage, BTW, is quite small (although Google is also trying to inflate that to gain sympathy). The copyrightability ruling applies only to "classical" software APIs; not protocols; not REST APIs etc.. There is no way, no how, to interpret the ruling to apply to anything other than this kind of API (copyright cannot apply to anything that isn't fixed). Implementation of an API by software that does not comply with the API's license is rare. In addition, implementation of an API for the purpose of providing a compatible, competing product may still be fair use. But that, too, is not what Google did. Android does not comply with not a single one of Java's editions, so it was certainly not Google's intention to create a competing implementation that would allow Java programs to run unchanged.
Android is the reason Java is the #1 programming language. I hope Google transitions to another language and leaves Java in the dust. Google is responsible for making Java relevant in the consumer space and Google is also going to be responsible for making it irrelevant thanks to Oracle.
Or Google could have complied with the open-source license, as they did with Linux. But there was no way Google was ever going to let that happen.
> Android is the reason Java is the #1 programming language
Android hardly accounts for a few percentage points.
How exactly did Google not comply? Are you suggesting that if Google released the Android bits under the GPL license and not the Apache they would be been compliant and Oracle would have not sued? I highly doubt that.
>Android hardly accounts for a few percentage points.
Java would be in a constant annual decline had it not been for Google and Android. Just as Objective-C has sunk dramatically in the TIOBE index we'll see the same result when Google switches to Go, Dart or perhaps even Python.
Of course! OpenJDK is licensed to the entire world under the GPL, and anyone is explicitly permitted to do whatever the hell they please with it.
OpenJDK is probably the world's second-largest open-source project (after the Linux kernel), and possibly the world's most active. OTOH, with the rare exceptions of Android (that has significant parts forked from Apache Harmony) and Go, Google has made scant contributions to open-source in general. Netflix, Yahoo, LinkedIn, Twitter and Facebook are all much bigger open-source contributors than Google. True, Oracle is not a big fan of the ton of open-sourceness it inherited from Sun, and has even made the terrible decision to stop contributing to OpenSolaris, but painting Google as a champion of the developer community and a defender of OSS is ridiculous. I have no love for Oracle, and even less love for Google, but in this story Oracle weren't the bad guys.
> Java would be in a constant annual decline had it not been for Google and Android.
That is completely unfounded. Even within Google (one of the world's biggest Java shops), Android is not one of the biggest Java codebases. Objective-C is a client-side language. Java is first and foremost used on the server. Client-side Java (including Android, which isn't really Java) is a very small part of the Java ecosystem.
Hardly. Java has been #1 nearly a whole decade before Android even appeared.
Java has been #1 from at least 2002 (and even before, long before Android) until now according to TIOBE -- the fact that it had a dip to #2 in 2014 doesn't change anything substancial to what I said, which was: "Java has been #1 nearly a whole decade before Android even appeared."
http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
No, I wrote (quote) "nearly a whole decade before Android was released".
Besides, you couldn't have missed the point more.
First the whole thing in discussion is whether Java became #1 due to Android or not (and it hasn't: it was #1 way before Android, and kept it until now for over a decade).
Second, TIOBE is indicative, not absolute. A language that's #1 with 25% in early 2014 doesn't suddenly drop 5-10 points to go below another for a few months -- that's just a momentary trend in searches or repos and other things that TIOBE looks at, not some indication that millions abandonded Java and adopted C for six months and then came back.