7 ms·
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
by bryanlarsen 6y ago
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 this is a great example to smack hackers with when they try and "hack" the law, treating it like code rather than something more human. It's a great example because this is a case where the majority is obviously the "right" decision to any true code hacker.
- quotemstr 6y agoI'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*.
- ghaff 6y agoThat'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.
- gfodor 6y agoI strongly agree with the outcome but the cost in the other direction is good API design is a creative process. If you sit down and design a kick-ass API for a year, another person who re-implements is inheriting that design, and its benefits, for free. I do wonder if another case will wind its way up one day where the defendant lifted the API not for interoperability but because it was a clean or clever interface. (Seems a bit far fetched but would round out fair use further I think.)
- quotemstr 6y agoEven if that happens, we'll still get beautiful APIs made. Copyright is a means to an end. Fonts, for example, are not subject to copyright, but we still see beautiful typefaces made.
- jacques_chester 6y agoThe majority opinion cited precedent (Feist) that copyright is not intended to profit the creator. It's to advance the progress of arts and sciences. If someone copies your amazing API, that sucks for you, but it's not stopping the progress of arts and sciences.
- gfodor 6y agoYes fair point I misread the OP that they were strictly talking about the legal tradeoffs. I was more thinking what was the actual cost to creators under this version of fair use.
- lostcolony 6y agoThey kind of intentionally danced around that question with 'are APIs copyrightable'. Because here it's allowable for a product that isn't competing, and is being leveraged for interoperability/ease of users to adopt (rather than for how clean/clever it is). What if someone had copied Stripe early on, though? Stripe's big claim at launch was "payment processing in 7 lines of Javascript" or similar. Obviously there were other barriers to entry, but what if someone else entered the market at that time with a similar (or even identical) interface? That question was left unanswered.
- bscphil 6y ago> 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.)
- VikingCoder 6y agoNo, when the code allows an exploit, that's a bug. Thomas is supposed to help us understand the intent of the code - what the Requirement was. Yes, it's better for us if the code reflects the intent perfectly. But to the degree that's not possible, we need someone to Interpret the code. Textualists are trying to ignore the fact that there's a difference between intent and implementation. The Legislature should do a far better job making their intent clear. But to the degree they make mistakes, leaving the intent unclear in some situation, it's good to have Case Law to inform us. I am not a lawyer. I don't know much about the law. But I do know metaphors, and when someone talks about exploiting the law, this is what comes to my mind.
- lostcolony 6y agoTangent, but you said something I find really telling, in conjunction with OP's post. Textualism to its proponents is very much like exploiting a system; figuring out the exact rules it defines and finding workarounds. It may not even be to a person's own goals (hence the individual not feeling biased when thinking this way), but is enjoyable in its own right in finding those loopholes (like the meme of the referee allowing Airbud to play, "there's nothing in the rule book!"). To its critics, it's like blindly implementing the ticket as written, rather than asking questions and making sure the intent is understood and the problem is being solved correctly. Which explains, in a surprisingly empathetic way, why I am not a textualist, and why some of my family are, when it comes to political discussions.
- zhengyi13 6y agoIn the D&D world that I'm familiar with, we call these sort of people "rules lawyers", and there too, they ruin the game for everyone.
- lostcolony 6y agoOh, 100%. I shared Thousand Year Old Vampire with a relative that matches this, thinking his love of history would make it an interesting thing, and his response was "I can already think of ways to beat the system", even before he actually read the system. It's like...yeah, it's a single player pen and paper RPG. You probably can. Why...why would you though? But that's what I mean; exploiting perceived flaws in the system is a greater goal -even when it ruins the game for themselves-. Because there is a greater sense of satisfaction in finding loopholes. And I understand that sense; I just find more value in understanding the underlying goal and intent and delivering on that.
- jcranmer 6y agoThomas'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.
- tantalor 6y agoThe argument from the text could go the other way: Congress didn't mention declarative code in the copyright act, so it's not included.
- 1980phipsi 6y agoThomas says the copyright act says any computer code called directly or indirectly. The Thomas argument is that this is an indirect use of code.
- tantalor 6y agoThomas doesn't understand basic computer programming, so I wouldn't put much weight on that nuanced view. "Indirect" here just means calling a function or jumping to some address, rather than directly inlining some statements. For the purpose of copyright, the term "computer code" does not include the signature of that function, or the address you jump to, only the actual code statements at that destination.
- wslack 6y agoWhich, I would argue, is out of step with how that language was understood at the time the legislation was drafted.
- InsaneOstrich 6y agoHe probably owns a bunch of Oracle stock
- Boxxed 6y ago> 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. Speak for yourself. There are plenty of us that understand you can't take the human element out of this.
- dundarious 6y agoThey said “tend to”...
- deleted 6y ago[deleted]
- TheMagicHorsey 6y agoJudge Thomas is terrible. He simultaneously says that corporations have First Amendment rights to donate unlimited money to politicians, but have no First Amendment rights to moderate content on their social networks. He's a hack that just does whatever is best for conservatives.
- bpodgursky 6y agoIf your worldview is this simple, it is also probably very wrong.
- TheMagicHorsey 6y agoBeing concise isn't simplistic. I explained very clearly what the contradiction in Thomas' rulings is which leads me to my conclusion. You can have an opinion about whether that's right ... but its hardly simplistic. Being simplistic would be having the view that he's a hack without any evidence. I don't say he's a hack lightly. If you look at his decisions he uses one path of reasoning in one set of decisions and then uses the opposite path of reasoning to come to a different conclusion in a different set of decisions, depending on how the outcome needs to come out. And then he claims he's being textual. Its nonsensical. Edit: TBF you're being very simplistic assuming my comment illustrates a worldview. What worldview is that? Look at my comment history. I'm generally free-market and maximal-corporate rights ... aligned with Thomas. I just think his reasoning is flawed.
- chelical 6y agoThere is a massive difference in interpreting law vs code. Code can be patched immediately. New laws or changes to an existing law can take months, even years or decades to pass.
- andomar 6y ago"Following the letter of the law" means ignoring Congressional intent. It allows the judge to choose one of the many possible readings of a statute. So in effect, "following the letter of the law" enlarges a judge's discretion. The opposite of what you would expect.
- jessriedel 6y agoNo, not generally. Congress is 545 different people, who definitely don't have a coherent collective intent. The only thing they did collectively was pass the text of the law. So any coherent notion of "congressional intent" has to mean the intent a person reading the text would infer about a hypothetical coherent author. I don't know anything about this particular case, but it is not at all true in general that there are more ways for a reader to interpret the explicit meaning of the written words than there are ways for a reader to interpret the intent of the written words.
- wslack 6y agoI think the intent is usually found in statements made by drafters of the legislative language. Intent is not packaged in the raw text of statute.
- jessriedel 6y agoYou can of course try to infer intent of individual drafters, or by looking at the transcripts of debates on the congressional floor, or by reading emails, or whatever. (I don't think this justified because these discussions aren't voted on, only the text of the law is, but I'm happy to put that aside as not everyone agrees with that perspective.) My point is that this needn't, and indeed generally isn't, a single coherent position, but rather is an incoherent mishmash of many competing interests. It will almost never be less ambiguous than the literal meaning of the words written on the paper, which is the claim I'm responding to. (You can certainly argue that it is better to follow this intent than the literal meaning, but that's different than the claim that the intent is less ambiguous.)
- 6y ago
- kemitchell 6y ago> It's a great example because this is a case where the majority is obviously the "right" decision to any true code hacker. https://en.wikipedia.org/wiki/No_true_Scotsman https://en.wikipedia.org/wiki/No_true_Scotsman Have you spoken to any professional language or API designers about this case? Would all "true code hackers" agree that copyright shouldn't apply to software at all?
- sgift 6y agoObviously, I cannot say anything about "all" API designers, but I've read the opinions of a good few of them, including some who wrote the APIs in question here (i.e. the Java SE APIs), and they were unanimous that making APIs copyrightable would be a horrible idea.
- CobrastanJorji 6y agoI think you're reading a different argument. Thomas's argument is circular dreck. It basically says: 1. An important fair use test is market effects. 2. Amazon and others used to give Oracle huge gobs of money because they feared that APIs might be copyrightable and not covered by fair use. 3. After Google called Oracle on this, Amazon and others also started believing it was likely fair use and stopped paying Oracle tens of billions per year. 4. Therefore, Google copying the API was a major adverse market effect. 5. Therefore, copying wasn't fair use. That's a shit argument. Watch me do a similar analysis in a more obvious way. 1. An important fair use test is market effects. 2. People used to pay gobs of money to watch the movie Transformers 2. 3. In a widely watched review of the film, I showed a 4 second clip of the movie where someone said "I am standing directly beneath the robot's testicles." 4. After this, nobody wanted to pay any money at all to watch Transformers 2. 5. Therefore, there was a major adverse market effect from my copying. 6. Therefore, copying wasn't fair use.