Live data from Hacker News

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

supremecourt.gov

141–150 of 965 posts

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

#141

I love how the Us supreme court judgements are written using low level terminology that most anyone can understand with little prior knowledge. Some countries use legal and complicated jargon that its hard to follow.

Based on my conversations with my wife, who is a lawyer, that plain language can be a little bit deceptive. While lawyers love their jargon and latin phrases, there's also a lot of very specific terms of art that sound like regular language. Terms like "reasonable" carry a lot of connotations and context in a legal decision that you don't get from the word alone. But yeah, I agree that these legal decisions are really easy for a layman to understand, even if I might miss some of the nuances.

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

#142

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…

I'm normally with the textualists on the court on the question of how we interpret the law, but in the case of copyright, the concept of "fair use" is specifically intended as an "extension point" where the courts could do what seemed right in changing circumstances. I like strongly typed languages too, but there are legitimate uses for void*.

That's a very good summary. This is a case where there probably is no legally "correct" decision based on the law/precedent. It comes down to fair use and to what degree you can reasonably extend it to this case. For most people reading this, the decision is the "right" one. But I'm not sure to what degree one side or the other is better supported as a matter of law/precedent.

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

#143
post #133

I would imagine if the ruling went the other way, IBM might want to talk to all the BIOS companies. Luckily, that didn't happen.

IBM would probably want to talk to 99% of computing companies out there, not just BIOS companies :-)

Including Oracle, since their copying of IBM's SQL API is what the whole company is based on.

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

#144
post #133

I would imagine if the ruling went the other way, IBM might want to talk to all the BIOS companies. Luckily, that didn't happen.

IBM would probably want to talk to 99% of computing companies out there, not just BIOS companies :-)

Including Oracle...

Good thing the SC saved Oracle from its own stupidity.

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

#145
post #112

Earlier quoted context omitted.

Upvoted because you shouldn't be downvoted into oblivion just for having an opinion contrary to the HN hivemind. It's okay to think Oracle should have won here. I disagree, but there are reasonable people on both sides.

In thought Oracle should have won this case as well and the opinion basically affirmed the reasoning but went the other way. The basis for Oracle winning was that copying the Java API for interoperability with developers rather than for existing software was copying for Java’s beauty rather than being purely functional. Whenever this case came up on HN people outright refused to acknowledge that one’s intentions even…

> copying for Java’s beauty rather than being purely functional

How would "beauty" be defined here. In the context of copyright, it would seem to apply to aesthetic beauty, but I'm not sure that applies to code (despite all sorts of engineers using the metaphor for theirs or others work).

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

#146

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…

I'm normally with the textualists on the court on the question of how we interpret the law, but in the case of copyright, the concept of "fair use" is specifically intended as an "extension point" where the courts could do what seemed right in changing circumstances. I like strongly typed languages too, but there are legitimate uses for void*.

> the concept of "fair use" was specifically intended as an "extension point"

Yes, but to a textualist how the law was intended doesn't matter! (I'm mostly joking, I agree with what you meant to say here, I think.)

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

#147
post #13

Earlier quoted context omitted.

Yep. This case was an existential threat to multitudes of industries and the assumptions they were built on. The weird thing is it would of hurt Oracle as much as anyone. I have no clue how anyone w/any technical merit didn't understand that this was a footgun of the largest possible magnitude for them.

I had the opportunity once to talk to an IP lawyer for Oracle and brought this up. I specifically brought up the S3 compatibility of their cloud storage among other instances. His reply was “without admitting anything specific, how do you know we haven’t purchased private licenses for anything you just mentioned?”

It's still silly. Imagine if you needed to purchase a license for the shape of plug that fits inside a standard plug socket - to build any appliance.

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

#148
post #79
post #65

Earlier quoted context omitted.

They didn't establish a new test, they applied the existing 4 tests / factors and found that they indicated fair use. The first 2 or 3 pages contain a description of the 4 tests and how they were found to apply in this case.

Not entirely. Per my understanding, this is a fairly big shift: "The fair use question is a mixed question of fact and law. Reviewing courts should appropriately defer to the jury’s findings of underlying facts, but the ultimate question whether those facts amount to a fair use is a legal question for judges to decide de novo. This approach does not violate the Seventh Amendment’s prohibition on courts reexamining fa…

That may be true, I remember there was quite a bit of surprise when the Court of Appeals overrode the fair use jury finding (not so much because they decided differently, but rather the fact that they set aside the jury's finding at all).

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

#150

Earlier quoted context omitted.

This is not a persuasive argument because, by your logic, function implementations are also mathematical formulas and everyone agrees that they are copyrightable.

The copyrightable part of them is the creative decision making used to organize the workings of the function itself, not the formulas. Two functions could have identical algorithmic performance, but be stylistically and semantically different, have been written independently, and neither would infringe on the copyright of the other.

An API design is also a creative and highly stylistic work. Anyone who has ever designed a large API, or suffered a poorly designed one, can attest to that. A bad design can work just as well as a good design.

Also, you are distorting the argument by making it about one method signature instead of thousands of interconnected types and methods that work together to present an ergonomic interface for the developer.

Post reply on HN