>This is a complete dramatization. Are you copying 10k lines of code from a licensed code base into your project without permission and using it in your commercial product? To point back to the substance of the thread and Oracle's claims... Google didn't copy any of Oracle/Sun's Java source code base into Android Java. Oracle lawyers acknowledge this. Instead, Google copied the API of function name spellings and also…
Here's a good analogy for non-programers. You're building a new car company. You see all the existing cars, the roads, and the garages. So you measure the width of the car and the garage and you decide that the car should be exactly 6' wide. Then you ship your car. Enjoy 15 years of market success. Then you find that Oracle created the first cars and says they have copyright on the width of your car. That's how stupi…
Google and Oracle's decade-long copyright battle reaches Supreme Court
291–300 of 433 posts
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#292>This is a complete dramatization. Are you copying 10k lines of code from a licensed code base into your project without permission and using it in your commercial product? To point back to the substance of the thread and Oracle's claims... Google didn't copy any of Oracle/Sun's Java source code base into Android Java. Oracle lawyers acknowledge this. Instead, Google copied the API of function name spellings and also…
Here's a good analogy for non-programers. You're building a new car company. You see all the existing cars, the roads, and the garages. So you measure the width of the car and the garage and you decide that the car should be exactly 6' wide. Then you ship your car. Enjoy 15 years of market success. Then you find that Oracle created the first cars and says they have copyright on the width of your car. That's how stupi…
That's how stupid car analogies are...
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#293Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#294Earlier quoted context omitted.
Here's a good analogy for non-programers. You're building a new car company. You see all the existing cars, the roads, and the garages. So you measure the width of the car and the garage and you decide that the car should be exactly 6' wide. Then you ship your car. Enjoy 15 years of market success. Then you find that Oracle created the first cars and says they have copyright on the width of your car. That's how stupi…
I don't think that's a good analogy at all. A car's precise width is not part of its interface nor a part of its design anyone particularly cares about. Its interface is more like, the design of the UX... how the steering wheel, dashboard, etc. look and feel. If a company copied those but changed everything underneath so that people could buy a cheaper alternative without seeing a difference on their usage... I don't…
We aren't talking about user interfaces here. This lawsuit does not involve UX. We are talking about interfaces between functional components. The analogy is spot on.
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#295Earlier quoted context omitted.
I don't think that's a good analogy at all. A car's precise width is not part of its interface nor a part of its design anyone particularly cares about. Its interface is more like, the design of the UX... how the steering wheel, dashboard, etc. look and feel. If a company copied those but changed everything underneath so that people could buy a cheaper alternative without seeing a difference on their usage... I don't…
The car's width is absolutely its interface with respect to roadway interoperability. We aren't talking about user interfaces here. This lawsuit does not involve UX. We are talking about interfaces between functional components. The analogy is spot on.
The lawsuit involves UX for a software framework. Which its API constitutes. The user happens to be a developer here and their usage is software development.
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#296Earlier quoted context omitted.
Here's a good analogy for non-programers. You're building a new car company. You see all the existing cars, the roads, and the garages. So you measure the width of the car and the garage and you decide that the car should be exactly 6' wide. Then you ship your car. Enjoy 15 years of market success. Then you find that Oracle created the first cars and says they have copyright on the width of your car. That's how stupi…
I don't think that's a good analogy at all. A car's precise width is not part of its interface nor a part of its design anyone particularly cares about. Its interface is more like, the design of the UX... how the steering wheel, dashboard, etc. look and feel. If a company copied those but changed everything underneath so that people could buy a cheaper alternative without seeing a difference on their usage... I don't…
Let's improve the analogy!
My proposal => that you chose to make the door handles six inches because of UX, and Oracle showed up and said they made theirs six inches before you did.
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#297Earlier quoted context omitted.
The car's width is absolutely its interface with respect to roadway interoperability. We aren't talking about user interfaces here. This lawsuit does not involve UX. We are talking about interfaces between functional components. The analogy is spot on.
The interoperability width is already set by the road... you're copying the road at that point, not the car. The lawsuit involves UX for a software framework. Which its API constitutes. The user happens to be a developer here and their usage is software development.
Your argument that the copying is once-removed is unfortunately irrelevant to copyright law.
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#298Earlier quoted context omitted.
The interoperability width is already set by the road... you're copying the road at that point, not the car. The lawsuit involves UX for a software framework. Which its API constitutes. The user happens to be a developer here and their usage is software development.
And this is why Google had to copy the interface -- otherwise their runtime would not operate with other existing products. As you can see given your example, the analogy is a perfect fit. Your argument that the copying is once-removed is unfortunately irrelevant to copyright law.
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#299Earlier quoted context omitted.
I don't think that's a good analogy at all. A car's precise width is not part of its interface nor a part of its design anyone particularly cares about. Its interface is more like, the design of the UX... how the steering wheel, dashboard, etc. look and feel. If a company copied those but changed everything underneath so that people could buy a cheaper alternative without seeing a difference on their usage... I don't…
> A car's width is not its interface. Let's improve the analogy! My proposal => that you chose to make the door handles six inches because of UX, and Oracle showed up and said they made theirs six inches before you did.
(For reference none of this is meant to reflect my position on what the law actually is, or should be. I'm just considering analogies here.)
Re: Google and Oracle's decade-long copyright battle reaches Supreme Court
#300Earlier quoted context omitted.
>If I'm understanding your argument, if Google independently developed a programming language, and then they implemented a compatibility layer that accepted Java bytecode invoking Java APIs and translated it in realtime to their not-Java programming language, then this would be okay? Yes >How would such a programming language be detectably different from being an implementation of Java? It would have it's own unique…
This doesnt make sence - you jyst replaced the textual API used at compiletime with a binary API used at runtime. Its literally same difference.
In this example Google independently developed a language and made it compatible with the JVM.
In the real world Google wanted Java and didn't like the licensing terms. So they copied the Java API and from that starting point built out their own version of Java.