I think the part that gets lost in all of this is that Sun offered to license Java to Google previously for $100M. [1] Google turned that down and bypassed Sun because they didn't want to pay (or license). At the time, Sun was happy to see Java being used by Google, even without the license. Still, Google knew exactly what they were doing. [2] My point is, they did this to themselves and they knew what they were poss…
> I think the part that gets lost in all of this is that Sun offered to license Java to Google previously for $100M. Google turned that down and bypassed Sun because they didn't want to pay (or license). I'm not sure I follow - Google believed they didn't need a license, just like everyone who used Linux despite SCO offering to license Linux to them. If Google needed a license, and Sun had not offered one, it would n…
Oracle Wins Revival of Billion-Dollar Case Against Google
371–380 of 643 posts
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#372Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#373It may be helpful for readers to look at the actual meat and potatoes of the decision itself. I recommend jumping in at Page 27 of the decision so that they can see how the fair use factors were evaluated in this case: http://www.cafc.uscourts.gov/sites/default/files/opinions-or... Fair use has four factors, lets see how it shook out: 1) Purpose and Character: Google tried to argue that because android is free that i…
So don't think of Java being in Android. The Android toolchain uses Java, but the Android runtime is not a Java runtime.
For one thing, this makes it different from Amazon using an Oracle Java runtime. But the total set of differences is deep and significant.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#374Earlier quoted context omitted.
It's more analogous to -- very analogous to -- the "clean room" BIOS clones that enabled the PC Clone industry to take off (and made IBM-compatible PCs actually affordable; before the clones took off, IBM's prices made Apple seem like a bargain).
Except Google did not do a clean room clone. They simply copied, thus violating the whole point of copyright. If they had developed their own API that simply used different names but was functionally identical, they would not have violated copyright. Copyright protects against copying . They didn't do that because they wanted to take advantage of the huge existing JAVA developer base who would easily be able to use t…
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#375Earlier quoted context omitted.
RE> Nature of the Copyrighted Work: Dealt with previously In my entire career you could not copyright an API. There is good reason for this. If you wanted to do business with certain entities, the implementation had to be multisource. The new implementation had to come from a cleanroom, but in this case it came from open source (which seems equivalent). Therefore you have one judge making one decision that is an anom…
There's a lot of similar responses regarding the API copyright issue. APIs have been 'subject to copyright' for 4 years, since the 2014 decision in this case. Lets see some key details: This is the 2012 ruling: http://www.groklaw.net/pdf3/OraGoogle-1202.pdf Alsup indicates that SSO isn't dead law, but finds that APIs aren't copyrightable because they are 'the only one way to write" things to get the key functionality…
Which premises are you referring to? I am not a lawyer, but I am a programmer, and what you just paraphrased sounded obviously true (at least when "the functionality" means "replacing the old system", a.k.a. interoperability).
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#376Earlier quoted context omitted.
> better That's it. The VMs on the market at the time we're absolutely terrible for phones. John Carmack was commenting on how JavaME gave you worse performance than an original IBM PC, and HotSpot's strategies absolutely destroy battery life.
Except that wasn't the only approach available. There are OEMs selling commercial JDKs for embedded use, with their own VM, JIT and AOT compiler variations, and library extensions. Contrary to Google, they always played by the rules.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#377Earlier quoted context omitted.
I sure hope so. That decision definitely needs to be appealed. I very much hope it's overturned. (The industry has pretty much assumed - and acted - that APIs were not copyrightable, and that's worked out all right. Suddenly shifting to APIs being copyrightable is going to cause some change the rules under existing activity, in ways that it's hard yet to define the full scope of.) But even if it's not, the decision n…
Didn't White House administration try to interfere with this case, and persuade judges not to declare APIs non copyrightable? That was really weird. https://arstechnica.com/tech-policy/2015/05/white-house-side... I wonder what will happen this time.
When the Supreme Court was considering Google's petition to hear the case, the court asked the White House to voice an opinion—where by "White House administration", you mean the Solicitor General.
That's not "weird"; that's a normal part of the job.
https://en.wikipedia.org/wiki/Solicitor_General_of_the_Unite...
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#378Earlier quoted context omitted.
There's a lot of similar responses regarding the API copyright issue. APIs have been 'subject to copyright' for 4 years, since the 2014 decision in this case. Lets see some key details: This is the 2012 ruling: http://www.groklaw.net/pdf3/OraGoogle-1202.pdf Alsup indicates that SSO isn't dead law, but finds that APIs aren't copyrightable because they are 'the only one way to write" things to get the key functionality…
Hi ABCLAW, I read page 17 and it is clearly written by someone that doesn't understand software. My non-lawyer reading of the justification implies that polymorphism violates copyright law - which is an even deeper issue. This would destroy all modern software development. Yikes! I am now even more confused. Even Oracle would disagree with this point of view. In your text, you are now making the argument that Google…
Regarding your polymorphism point, you've got the cause and effect swapped. The LACK of polymorphism was the basis for Alsup saying APIs are uncopyrightable. Because there's only one way to do something, the words and the function are linked, and copyright does not protect function, ergo copyright wouldn't protect the word either. This line of reasoning doesn't flow in reverse - Polymorphism doesn't indicate that a work is copyrighted or subject to restrictions upon use, or that various safe harbour provisions/copyright exceptions do not apply.
2) There's no need for a separate discussion. I'm not making the argument; it's literally admitted by Google in the context of this case that they straight up copied chunks of code.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#379Earlier quoted context omitted.
Didn't White House administration try to interfere with this case, and persuade judges not to declare APIs non copyrightable? That was really weird. https://arstechnica.com/tech-policy/2015/05/white-house-side... I wonder what will happen this time.
That's an interesting way to characterize it. When the Supreme Court was considering Google's petition to hear the case, the court asked the White House to voice an opinion—where by "White House administration", you mean the Solicitor General. That's not "weird"; that's a normal part of the job. https://en.wikipedia.org/wiki/Solicitor_General_of_the_Unite...
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#380Appellate courts do not lightly overturn jury verdicts using highly fact-specific reviews of evidence. There is a reason they call a jury a "trier of fact". There is a reason for this: if it were the rule that an appellate court could easily step in and second-guess how a jury weighs evidence, there would be little room for finality with jury verdicts because lawyers are very skilled (and become very tiresome) endles…