It 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…
Oracle Wins Revival of Billion-Dollar Case Against Google
271–280 of 643 posts
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#272I’m not sure if I have the timeline correct but I thought Java was owned by Sun Microsystems at the time when they made these decisions. I’m sure they rightly assumed Sun Microsystems would never do this. It is sad to see what Oracle is doing with Sun Microsystem’s creation.
The following is the fun history: - Java is created / owned by Sun. - Sun was fearful of MS's EEE approach (embrace, extend, exterminate) where MS took a thing, built their own, pushed their own tooling, added their own proprietary instruction, boom windows lock-in. So Sun basically made their contract: Java is free but only if you DO NOT introduce any new instructions, and implement a 100% compatible VM, nothing add…
They just didn't had enough money to sue and decided to make juice out of lemons.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#273Earlier quoted context omitted.
The court has made the point now that literally just the class and method names are subject to copyright.
I thought Google used the implementations!
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#274It 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…
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 anomaly. It seems to me that a single judge should not be making a landmark decision.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#275I 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…
Google believed they could implement their own VM and get something cheaper (and/or better) than they would get by licensing one from Sun. That seems like a perfectly legitimate business decision for them to make. A clean-room reimplementation of an existing API had long been thought to be legally clear, going all the way back to Compaq reimplementing the IBM BIOS and starting the "IBM-compatible" competitive ecosyst…
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#276Earlier quoted context omitted.
> reverse engineering That is certainly an issue if you reverse engineer anything. Google went out of their way to NOT reverse engineer it. The issue is can a public API be copyrighted. That is the scary issue.
I don't get why it's a scary issue or even controversial why an API would be subject copyright. An API, in my mind, is similar to design drawings or blueprints. Independently figuring out how to implement those drawings doesn't change the fact that you copied the design.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#277Earlier quoted context omitted.
> reverse engineering That is certainly an issue if you reverse engineer anything. Google went out of their way to NOT reverse engineer it. The issue is can a public API be copyrighted. That is the scary issue.
I don't get why it's a scary issue or even controversial why an API would be subject copyright. An API, in my mind, is similar to design drawings or blueprints. Independently figuring out how to implement those drawings doesn't change the fact that you copied the design.
Take this as an example: https://docs.us-phoenix-1.oraclecloud.com/Content/Object/Tas...
Here is an example of a potential copyright infringer copying the API for another competing service. I'd hope they acquired a license for it, otherwise.
Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#278Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#279Re: Oracle Wins Revival of Billion-Dollar Case Against Google
#280It 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…
IANAL, but doesn't this contradict case law elsewhere?