-- 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.
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.