Linked by Thom Holwerda on Thu 31st May 2012 21:41 UTC
Legal And thus, it ends. Despite a never-ending stream of doom and gloom from Oracle/Microsoft-funded 'pundits' regarding Google and Android (six hundred billion trillion gazillion eurodollars in damages!!1!), judge Alsup has just squashed all of Oracle's chances with a ruling that is good news for those of us who truly care about this wonderful industry: APIs are not copyrightable. Alsup: "To accept Oracle's claim would be to allow anyone to copyright one version of code to carry out a system of commands and thereby bar all others from writing their own different versions to carry out all or part of the same commands. No holding has ever endorsed such a sweeping proposition." Supreme Court, Ellison?
Thread beginning with comment 520354
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by shmerl
by phoenix on Fri 1st Jun 2012 16:30 UTC in reply to "RE[7]: Comment by shmerl"
phoenix
Member since:
2005-07-11

Except that Java *itself* is fragmented, and is not interoperable with itself. Afterall, the APIs available to a J2ME developer are not the same APIs available to a J2SE developer, which are not the same APIs available to a J2EE developer. And that is all Oracle's (originally Sun's) doing!

The problem with Oracle's entire case against Google/Android is that they keep changing their demands/arguments. They don't actually have a case, which is why they keep changing their demands/arguments.

Reading through the Groklaw coverage of the case, it's amazing it even made it to court, let alone made it through the complete trial. There was never any possibility of Oracle winning. Their lawyers and arguments were specious at best, and downright wrong most of the time.

Reply Parent Score: 4

RE[9]: Comment by shmerl
by JAlexoid on Sat 2nd Jun 2012 01:02 in reply to "RE[8]: Comment by shmerl"
JAlexoid Member since:
2009-05-19

You forgot JavaRT. Java Card and a whole lot of other API sets that are very much incompatible with Java SE.

Reply Parent Score: 3