Earlier quoted context omitted.
I'm glad about this outcome, because I agree the other outcome would have had a devastating effect on software development. I also appreciate this fair use argument, especially when you point out the code in question was 0.4% of the entire API. Still, I'll always struggle with the idea that "the amount and substantiality of the portion used" when copying an interface is comparable to copying an implementation. The in…
if I remember my history correctly Google did not, Android was purchased by Google by that time the choice to use Java SE as the API was already made
Google’s copying of the Java SE API was fair use [pdf]
561–570 of 965 posts
Re: Google’s copying of the Java SE API was fair use [pdf]
#562Earlier quoted context omitted.
While I agree that APIs should not be copyrightable, the Supreme Court has been criticized for "legislating from the bench". Avoiding the temptation to set bigger and more far-reaching precedents than is strictly necessary for the case at hand avoids giving the impression that the judicial branch is doing the job of the legislative branch.
This is something I struggle with, personally. I have fundamental problems with an unelected council that serves for life creating law. However, we have an extremely inefficient form of Government that doesn't allow for quick adaptation, and legal questions will arise tomorrow that did not occur to legislators today. The courts are supposed to help resolve any ambiguity. The question over whether or not APIs are copy…
If your democratically elected legislators don't like a bench ruling, they are free to make a new law that specifically overrides that ruling. The legislature is the ultimate source of authority in the land. The courts only have a bit of wiggle room in interpreting unclear statutes.
The system is designed well. Unfortunately, democratically elected legislators at the moment would rather obstruct, wreck, and go on wild-ass conspiracy rants, than legislate.
If that legislature spent half the time it complains about activist judges actually drafting law, it would have nothing to complain about. If you, as a constituent are unhappy about the current state of affairs, vote in legislators who are willing to do their job.
Re: Google’s copying of the Java SE API was fair use [pdf]
#563Earlier quoted context omitted.
Justice Thomas wrote explicitly that he thought the majority blurred the lines between implementation and declaration. I think he's wrong by virtue of some disability to follow the winning argument logically. Clarence is sheer idiot.
Please make your substantive points without calling names. https://news.ycombinator.com/newsguidelines.html
Re: Google’s copying of the Java SE API was fair use [pdf]
#564Re: Google’s copying of the Java SE API was fair use [pdf]
#565Earlier quoted context omitted.
An alternative take, which I'm sure won't be popular, is that now, with an interpretation taken to the extreme, a megаcorporation can basically steal your (let's say a small startup's) platform (in case you refuse to sell it for ethical or some other reasons), by re-implementing it and investing much more resources which you don't have, to make it more attractive to customers. I'm ok with either decision, but, depend…
I think that's always been a threat. If a large business decides to target an area you develop a system for, you're basically out of luck unless you have some novel IP that's difficult to replicate. You really have to have something niche, patent it, etc. otherwise you just roll the dice that massive entity X doesn't steamroll your livelihood out of business.
Re: Google’s copying of the Java SE API was fair use [pdf]
#566Re-implementing an API is how we got clone PC's when Compaq cloned the IBM BIOS interface and associated ISA bus logic which made Intel based DOS home computers cheaper and affordable for ordinary people.
Re: Google’s copying of the Java SE API was fair use [pdf]
#567> "Google copied approximately 11,500 lines of declaring code from the API, which amounts to virtually all the declaring code needed to call up hundreds of different tasks. Those 11,500 lines, however, are only 0.4 percent of the entire API at issue, which consists of 2.86 million total lines. In considering “the amount and substantiality of the portion used” in this case, the 11,500 lines of code should be viewed as…
Re: Google’s copying of the Java SE API was fair use [pdf]
#568> "Google copied approximately 11,500 lines of declaring code from the API, which amounts to virtually all the declaring code needed to call up hundreds of different tasks. Those 11,500 lines, however, are only 0.4 percent of the entire API at issue, which consists of 2.86 million total lines. In considering “the amount and substantiality of the portion used” in this case, the 11,500 lines of code should be viewed as…
I wouldn't celebrate a victory yet. As is often the case, the court's choice of tests simply will serve as a blueprint for others on how to avoid themselves being caught in the same kind of result. Based on this court decision, it's apparently fair use to lift someone else's API and use it to jumpstart programmer familiarity with your product, if the author of the API previously tried to achieve success in that narro…
Re: Google’s copying of the Java SE API was fair use [pdf]
#569Earlier quoted context omitted.
I wouldn't celebrate a victory yet. As is often the case, the court's choice of tests simply will serve as a blueprint for others on how to avoid themselves being caught in the same kind of result. Based on this court decision, it's apparently fair use to lift someone else's API and use it to jumpstart programmer familiarity with your product, if the author of the API previously tried to achieve success in that narro…
> IP holder companies will become even more common: they will be used to hold copyright to one API and license it out to customers Not after this precedent, which says that APIs are free. What will happen: Intel licensing the i86 instruction set will not be possible from now on, same for ARM.
No, it doesn't. It says the "fair use" doctrine covers copying an API's "task calling" system, i.e. nomenclature and ontology.
Re: Google’s copying of the Java SE API was fair use [pdf]
#570Earlier quoted context omitted.
No but it’s okay to copy all the entry names in the encyclopedia and fill in the content yourself
This is an excellent metaphor but now I am curious, is it literally true?
Certainly, the fact that competing encyclopedias exist, and have for hundreds of years, with > 99% identical entry names (but of course, substantively different content), and that predicated not on any given invention or IP but rather the common use English language, would, I think, make the judges rather reluctant to rule differently even should there be 100% match in entries.