Live data from Hacker News

Google’s copying of the Java SE API was fair use [pdf]

supremecourt.gov

191–200 of 965 posts

Re: Google’s copying of the Java SE API was fair use [pdf]

#191
post #165

This is one of the most important legal decisions in the history of software. The US Supreme Court has basically just saved the whole software industry (and FOSS projects) from being wrecked by patent trolls.

Why? It wasn’t about whether APIs are under copyright (they are), but whether this particular case constitutes fair use. I think the effect of this decision was way overblown.

If this wasn't fair use, nothing of any substantial value could be considered fair use.

Re: Google’s copying of the Java SE API was fair use [pdf]

#192

Earlier quoted context omitted.

I'm glad for the verdict but this is such bullshit. Google implemented exactly enough to create the illusion of letting people use their Java talents then dragged their feet with a half broken out-of-date language environment. And they did all this to save money, not some sort of noble rebellion or clever hack. > Sun offered a licensing deal of between US$30 and 50 million. Schmidt said Google would have paid for tha…

I don't know why people are acting like this is some victory of open source I don't know that anybody is saying that Google did anything specifically Good or Just or Noble or anything. The celebratory aspect is more based on all the Bad Things that would have happened in the future if this decision had come down in favor of Oracle.

What bad things would have happened? This ruling specifically says that it was fair use, not that APIs are copyrightable - which seems to be the buggy man. As it currently stands, APIs absolutely fall under copyright laws.

Re: Google’s copying of the Java SE API was fair use [pdf]

#193
post #165

This is one of the most important legal decisions in the history of software. The US Supreme Court has basically just saved the whole software industry (and FOSS projects) from being wrecked by patent trolls.

Why? It wasn’t about whether APIs are under copyright (they are), but whether this particular case constitutes fair use. I think the effect of this decision was way overblown.

It definitely sends a message. And the stakes were so high that the message is know very loud and clear, too.

Re: Google’s copying of the Java SE API was fair use [pdf]

#194
> In this way, the declaring code’s shortcut function is similar to a gas pedal in a car that tells the car to move faster or the QWERTY keyboard on a typewriter that calls up a certain letter when you press a particular key. As those analogies demonstrate, one can think of the declaring code as part of an interface between human beings and a machine.

I love this analogy, and I'm going to use it to describe this case from now on. If I have a great idea for a new keyboard, maybe great new clicky keys or something, I have to make it QWERTY. I can't just come up with some random key ordering. And it has nothing to do with how good or bad QWERTY is as an idea. It's just that QWERTY happens to be what people have skills in.

Re: Google’s copying of the Java SE API was fair use [pdf]

#195

This is one of the most important legal decisions in the history of software. The US Supreme Court has basically just saved the whole software industry (and FOSS projects) from being wrecked by patent trolls.

Good, now can we get a ruling that prevents Google, RedHat, Microsoft and others from wrecking FLOSS projects with their stifling influence? Or prevent them from eradicating competing or even original projects by doing hostile rewrites or forks?

Should we also get rid of all of GNU's hostile rewrites?

Re: Google’s copying of the Java SE API was fair use [pdf]

#198

For better or worse, the same arguments ( "API is copyrightable" ) is what was used in the past to prevent 98's Microsoft from doing embrace-extend-extinguish to Java with their "JavaVM with P/Invoke'd Win32 API". The idea in that case was that when you try to implement something identical to the Java language and standard library, it doesn't matter if you call it Java or "Visual J++"; you are still implementing Java…

The issue is that what Sun was trying to do to Microsoft was equally wrong, but people didn't care as much because Microsoft was more obviously the villain.

The real answer is that copyright is the wrong tool to go after what Microsoft did and the correct tool for that is antitrust. EEE is anti-competitive even if copying an API is fair use.

Re: Google’s copying of the Java SE API was fair use [pdf]

#199

It's interesting reading Thomas' dissent. As per typical Thomas appears to be arguing that it's the letter of the law that matters, whereas it's the majority opinion that the motivations and substance of the law are primary. Hackers and programmers tend to try and read the law like computer code to be "hacked" and exploited based on the letter of the law. So you'd expect us to be more sympathetic to Thomas' view. So…

Thomas's analysis pretty much starts from the conclusion that Google made billions off of Android, so therefore how could anything it be copied be fair use? He cloaks this analysis somewhat by arguing that the distinction between declaring and implementing code must be meaningless because Congress didn't lay it out explicitly in law, but for the person who actually broached the question of what other factors might influence fair use during oral arguments, it's pretty unintrospective about the analysis itself.
Post reply on HN