Oracle V. Google Being Decided By Clueless Judge and Jury (vice.com)
theodp writes: The problem with Oracle v. Google," explains Motherboard's Sarah Jeong, "is that everyone actually affected by the case knows what an API is, but the whole affair is being decided by people who don't, from the normals in the jury box to the normals at the Supreme Court." Which has Google's witnesses "really, really worried that the jury does not understand nerd shit." Jeong writes, "Eric Schmidt sought to describe APIs and languages using power plugs as an analogy. Jonathan Schwartz tried his hand at explaining with 'breakfast menus,' only to have Judge William Alsup respond witheringly, 'I don't know what the witness just said. The thing about the breakfast menu makes no sense.'
"Schwartz's second attempt at the breakfast menu analogy went much better, as he explained that although two different restaurants could have hamburgers on the menu, the actual hamburgers themselves were different -- the terms on the menu were an API, and the hamburgers were implementations." And Schwarz's explanation that the acronym GNU stands for 'GNU is Not Unix' drew the following exchange: "The G part stands for GNU?" Alsup asked in disbelief. "Yes," said Schwartz on the stand. "That doesn't make any sense," said the 71-year-old Clinton appointee.
"Schwartz's second attempt at the breakfast menu analogy went much better, as he explained that although two different restaurants could have hamburgers on the menu, the actual hamburgers themselves were different -- the terms on the menu were an API, and the hamburgers were implementations." And Schwarz's explanation that the acronym GNU stands for 'GNU is Not Unix' drew the following exchange: "The G part stands for GNU?" Alsup asked in disbelief. "Yes," said Schwartz on the stand. "That doesn't make any sense," said the 71-year-old Clinton appointee.
Please let them bring up PHP for some reason...
He couldn't just bring up steering wheel, accelerator, brake, and gear shift as an example of an interface?
Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
It's not clear to me that the problem is the judge and the jury. The analogies seem like they're pretty bad analogies, especially the breakfast menu. It seems like the problem is just as likely that the lawyers and expert witnesses are doing a bad job of explaining things to the jury. Why do things have to be dumbed down, anyway? Why not directly explain what an API is instead of resorting to simplistic analogies? Instead, the judge and jury are accused of being clueless. Perhaps you should listen to the judge that the analogies are confusing instead of claiming the judge and jury are idiots. Maybe people don't like being talked down to. Somehow I have a feeling the judge and jury actually care about understanding what an API is, and resent that witnesses are talking down to them.
The judge isn't wrong, having a recursive name like GNU is weird and something only nerdy programmer types really appreciate.
This trial is a prime example of a concern I often have with the legal system in particular and the government in general: people who do not understand something are being asked to decide an issue. Government officials, whether they are judges, lawmakers or the leader of the country are usually well versed in law, but not medical research, technology, engineering, education and rarely have first hand experience with poverty, womens issues, etc. I think it's an unfortunate side effect of our system.
Unless the gnu lives on Endor.
Why was SVN so slowly adopted?
Well, which CEO wants a software tool in house that is called "subversion" and the main IDE integration was called "subversive"?
Why do we have a program called "less"? Who is old enough to remember that the original program was called "more"? ... once ... but actually it is not. From a today perspective calling a program "less" which's only purpose is to display "more" makes no sense at all.
A program that displayed its input page by page and had in the last line "hit space for MORE". Calling the improved version of "more" "less" might be funny
There are more funny plays of word like this, e.g. the first improved "man" program, that was worth installing was called "woman". Yea, funny ... I was like 23 when I installed it (on request of my 'boss' a guy making his PhD).
Hm, to tired now, I had 3 or 4 more examples but nothing comes to mind right now.
I would not be surprised if there is an improved version of "cat" that is called "dog" ...
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
What the f... does the average person really know about running a country? Nothing. Why should he have any say in that, really? Couldn't we just leave it to a bunch of experts? And what's to say the experts are really neutral at anything? For example if you wanted "experts" on copyright law you'd probably end up with a jury full of MPAA/RIAA/BPA members, oh and maybe a couple from the EFF for balance and surprisingly most their verdicts would go in favor of big business. Having ignorant people on the jury is the worst of all systems, except every other system we've tried. If you think you can design a system that won't have these problems you're either absolutely brilliant or extremely ignorant. And I know what my money is on.
Live today, because you never know what tomorrow brings
These are people (the jury) who failed geometry in high school. And that was when he subject material of proofs and theorms (and logical arguments like programming) was fresh in their minds. The average American struggles with 6th grade pre-algebra - and I'm talking college grads more than 10 years out! Most of my (non-tech, 40-something, BS or MS degreed, commercially successful) parent friends are basically tapped out of helping their own kids in math by 7th grade.
You could explain APIs from now until 2020 and half of them still wouldn't get it. An analogy involved food/restaurants (which they DO understand) may be your only hope, since sex and excretory functions are off the table in terms of polite conversation.
Is it just my observation, or are there way too many stupid people in the world?
This actually sounds somewhat like what the American justice system is *supposed* to be like. The goal is justice, not understanding by the jury. Both sides present their best cases - hopefully both do so competently so that lay people can understand what the important facts are. The jury then decides the various disputed points based on that evidence and their understanding as lay people. Experts are supposed to explain things to them clearly. The judge's actions also appear correct. His job is to facilitate the understanding that the jury forms of the evidence. If something seems muddy to him then he can expect it to be muddy to the jury and the presenting side can, as in this case, present that part more clearly. The counsel of the side not presenting the muddy breakfast menu may be displeased when the judge causes that to be explained again more clearly. At the end of the day, jury needs to have enough understanding to know which side should prevail on which issues and also to decide the penalty.
This could work to our advantage.
Judge: So, exactly what is recursion?
Definition: recursion; see recursion
Supreme Court is now stuck in an endless loop, never to bother us again.
Have gnu, will travel.
And if intent meant anything, Gore won Florida. By more than 48000 votes (butterfly ballot).
but it doesn't.
Hillary had nothing to do with it
Is there any other kind?
I give you Loreena Bobbit, who emasculated her drunk husband for sexing it up with another woman, then cried "rape attempt" and was LET OFF though there was zero evidence of the claimed rape.
As the biker's said years ago " Remember that at trial, your future will be decided by 12 people so stupid they could not think of an excuse to get out of jury duty.
>normals in the jury box to the normals at the Supreme Court
Who talks like this? The whole tone of TFA is cringe-inducing. Couldn't the submitter find another article about this lawsuit that reads like it was written by adult?
The whole point of pre-trial proceedings is to frame the issues in a way that a judge and jury can understand them. If you are not focused, if you are not making yourself clear, this is the time and place to fix the problem.
Judge Alsup writes code
Quote from this judge from this same case before the appeal I believe
I have done, and still do, a significant amount of programming in other languages. I've written blocks of code like rangeCheck a hundred times before. I could do it, you could do it. The idea that someone would copy that when they could do it themselves just as fast, it was an accident. There's no way you could say that was speeding them along to the marketplace. You're one of the best lawyers in America, how could you even make that kind of argument?
Really? I see this as no different to a 3rd party manufacturer making coffee pods or oil filters. The API is the bit that connects / fits with something on the outside. And I can do it both ways. I can make a coffee machine that uses nespresso pods or I could make pods that fit in a nespresso machine.
Who puts hamburgers on a breakfast menu?
Good grief. Really? REALLY? From first principles, assuming only that someone has used a reasonably modern computer:
1) The purpose of a computer is to perform various series of small steps, called "instructions", assembled in an order such that each whole series of instructions can perform a more complex task than a single instruction can by itself.
2) These assemblies of instructions are called "programs."
3) Computers can have previously prepared programs built-in, or installed later, that are designed to provide certain services to other programs, so that these services do not have to be re-created for every new program that needs them, and so that these services are performed in a standardized way for all programs that need them.
4) An API is the part of the previously prepared program that provides the means to access these services. The term means "Application Programming Interface" or "Application Programmer Interface."
5) An example of this is the window that opens when you want to select a file from within a program such as a spreadsheet or a word processor. This is often called a "file dialog." In order that users of computers only have to deal with one set of tools to open files, this service is provided by modern computer operating systems, and is often preferentially used instead of creating one's own version of such a function. The API for this service allows for asking that the dialog be opened, and then, when the user chooses one or more files from the list in the dialog, the returning of which file(s) the user picked to the program that requested the file dialog service. There are other services provided in the API, including "cancel", when the user changes their mind about choosing a file; change the storage location where the chosen file will, or does already, reside, and so on.
---
It's not trivial to actually explain, but it isn't all that difficult, either. I'm sure there are others here who could do much better than I. Without ever mentioning a... menu, etc.
I've fallen off your lawn, and I can't get up.
If you think "normals" are bad, try dealing with users as a system admin tech. "No, sir," I would explain. "The computer doesn't belong to you. It belongs to the company. And I have full authority to fix your computer." Some days I wish I could replace their computer with a box of crayons, which is all they need to do their job anyway.
If they're copyrightable then surely there aren't any *books* about Java not written by Oracle right? After all, a book couldn't mention them without violating copyright. Yes?
GNU is a recursive acronym. The best non-tech example I can think of is VISA, which stands for Visa International Service Association. The judge probably has a VISA card himself.
From what I've seen during jury selection, demonstrate either knowledge or the ability to think for yourself and you will be dismissed post-haste. The lawyers for both sides (criminal or civil) want more-or-less house plants that will follow their version of "logic".
Anyone who has followed the United States political scene since, essentially, forever (about 1796, or thereabouts) knows that our system is fully intended to maximize the power of the dimmest bulbs in the shed.
You know, people maybe uninformed on minutia of a specific field but they are still trying their best to understand it, the first court decision probed that point. I wouldn't be so quick to call anybody clueless. On the other hand this could be a case of corruption, after all we are talking about Oracle and Larry here.
AFAIC Larry and Oracle lawyers in this case should be held personally responsible for all of this. If I were running Google (Alphabet?) I would be taking other measures, planning steps to stop these proceedings by means that have nothing to do with any court... We are talking about billions ( or more) here and about every application and system out there. Beside planning a hit on Oracle and its key people, I would also be working on the government level, trying to dismantle the entire copyright/patent system. Government must not have the authority to protect any company or individual from competition.
You can't handle the truth.
> 3rd party manufacturer making coffee pods or oil filters.
This analog does not hold, for the reason that it's not covered by copyright. Copyright involves text content, basically sequence of letters. Those sequence of letters get copyright protection, if it's unique. Api definitions are text content like that.
The key in regognizing copyrightable content is that there exists large number of possible arrangements (of letters), but authors choose their unique combination. Simply duplicating it is illegal, because doing so is easier than choosing the combination from scratch.
> Why do I suspect that you don't really know what an API really is?
I'm a programmer. Even though api has smaller state space than ordinary text content, it still contains enough freedom for authors to choose their unique implementations. Thus it gets copyright protection. Assuming otherwise is dangerous.
The entire software industry would grind to a halt if a copyright on APIs were enforced. Do you think someone should be able to sue Oracle for using SQL as the interface to their DBMS? Or using the Unix API in Solaris? Solaris ships with a C/C++ compiler and I'm pretty sure Sun/Oracle "stole" the APIs from AT&T and UCB. I don't see how this is any different from Android.
> The entire software industry would grind to a halt if a copyright on APIs were enforced.
I think you underestimate the problem. It's much worse than that. Companies would need to build their own markets for their software, instead of always building their wares utilizing someone elses market. The trick is that this would be useful activity for a company to do. Now that they skip the hard work, consumers will suffer because the services are simply not available where they're needed.
If you make APIs copyrightable, you do extreme economic damage by enabling monopolies. Copyright is not a natural right. Its only purpose is to assure that people cannot just copy creative works by others and thereby stop the creation of such works. In the case of an API, this is not a risk, because an API without an implementation is worthless, and the implementation is covered. It is also highly doubtful that an API is a creative work at all.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
In the first trial, which Alsup ruled that an API is not subject to copyright. He learned Java for the case and written that even a high schooler could write it in 10 minutes.
https://developers.slashdot.or...
Fight Spammers!
But my understanding is that they are duplicating an implementation via black box reverse engineering. Anything can be described in words, this doesn't extend copyright protection to the final object.
If your interpretation is correct there would be no need or desire for software patents of any kind because software is collections of letters and hence fall under copyright. This just simply isn't the case.
> You think the government should protect corps from entering each others' markets?
That's why companies apply for patent protections, so that other companies don't immediately conquer your market with significantly bigger resources than you have. Copyrights have similar purpose, authors don't want publishers conquering the market with _copies_ of his own books. It takes several years to write a book, and if other publishers don't need to spend that time to get the same result, it's unfair to the author who did need to spend that time.
The problem here is that oracle don't have a design patent, which is what you are talking about. If you have a design patent for the API, then this whole thing would have been a different story. For example the pod is patentable in its design. You are not allowed to make one that looks identical without violating the design patent. The invention itself of the idea of a pod is also patentable, and that patent would be violated by making any pod.
Instead of oracle arguing its a design infringement, they are instead only have an invention patent on the way java works as a virtual machine concept.
So google will win as they haven't taken the concept of the whole java machine, but they have taken the design in terms of form and fit the design takes.
By default, everything you scrible to a piece of paper, or a text file gets copyright protection
Right, but the scribbles aren't the recipe - they're a *representation* of a recipe. The recipe itself is an abstract idea. Should I have copyright on the number 5 just because I wrote it in text? Similarly, the code that describes an API is not the API.
Ceci n'est pas une pipe.
> But my understanding is that they are duplicating an implementation via black box reverse engineering.
from the paperwork, it didn't sound like black box reverse engineering... Instead they copy-pasted the api definitions and then implemented the missing functions. This requires no reverse engineering activity. It just requires a text editor + some programmers to write new code based on _existing_ api specification. But they had no reason to assume that they are allowed to use that specification.
but if you're reading some other paperwork, maybe i missed the information ;)
No one bothered to challenge Schwartz’s apparent belief that hamburgers are commonly featured on breakfast menus, as he had already moved on to confusing the jury on another front
“You don't remember this article about being one of the fifteen worst CEOs in American history?” [Oracle's lawyer] asked him.
Schwartz congratulates Google on developing an open source mobile platform to its face, and then calls it “Scroogle” in a private email
btw, this case isn't the end of the world, it won't affect your ability to use APIs, only to copy them wholesale. And even then you can have a defense if you do it for interoperability purposes, so in 90% of the cases where you'd want to copy an API, you'll be able to.
In the other cases, make up your own stupid language, it's not like Java is that great.
"First they came for the slanderers and i said nothing."
This isn't the nerds versus the suits, it's one businessman-nerd against a bunch of non-businessmen nerds.
These are super nerds. They're so smart that they cast baffled-courtroom-of-nerdrage at the jury, unfortunately lining up to only win this dungeon on the next roll with a perfect 12.
-1, irrelevant
The Appellate Court stipulated that APIs are copyrightable when they remanded the case back to the lower court. Not argument that they are not copyrightable is being entertained in this court. They have to get back to the Appellate Court to challenge that stipulation.
Be careful of mistaking a judge who is unaware for a judge that is letting counsel have enough rope to hang themselves.
Well, yes, I actually do think that someone (IBM) should be able to sue Oracle for using SQL, in the abstract. In reality when IBM offered SQL to ANSI they agreed to make it zero license. Of course, all users of SQL add non-standard extensions to make it not-really-interoperable, in order to keep their own edge. Those extensions are often not licensed to third parties (although sometimes are, and those licenses end up making strange movements over time based on mergers and such, which actually often ends up with them being opened, or they find their way into future standards with zero-license clauses).
The AT&T SVR4 API was in fact licensed by Sun (and HP and IBM), at considerable expense. These licenses continued to be paid until Novell released the SVR4 license and Unix name to The Open Group. SCO has attempted to collect on later SYSV licenses, with little success, but that is only because most forks were legal variants of SYSV made before the revisions that SCO controlled.
It's not different from Android, and historically APIs have been licensed.
Are you saying... the jury is not "of your peers"?
In this case yes. The definition of peer (From Oxford Dictionaries Online) - "A Person of the same age, status or ability as another specified person" As those involved in this trial are legal not natural persons, the 'age' part does not apply, for the 'status' to apply the jury would have to be legal, not natural persons and as to whether individuals people can have the same abilities as a corporation ...
The text that expresses the API is what's copyrighted, the idea that's expressed is not. 17 USC 102(b) denies protection to "any idea, procedure, process, system, method of operation, concept, principle, or discovery". This is deliberate, denying protection to functional aspects among other things.
This is even more explicit in "pictorial, graphic and sculptural works", where the very definition of them excludes utilitarian aspects.
While 102(b) does not deny protection to the expression of those functional ideas, when there are very few ways to express that idea, when the expression is inseparable from the idea, then the idea and expression are said to merge, and the denial of protection to the idea applies to the expression as well.
With source code implementing an API, the idea expressed is that API. When there is only one way to express that idea, then the expression itself is denied protection.
The parts of the Java API that define the names and types of the various elements are the declarations, and there is only one way in Java to express them without changing the meaning and functional specifications for the API being expressed. Thus, Google's declarations are going to be almost identical to Oracle's, and that should not be infringing.
The code that implements the methods can be written in many ways, usually, so protection remains intact for that portion, even though the idea (what that method is supposed to do) is still an unprotected idea. Google is allowed to re-implement the code for a method because the idea is not protected, but they can't copy the actual code from Oracle, since that is protected by copyright.
Clean room reverse engineering can be used to prove you didn't copy protected expression, that any similarities are purely by chance, but since the jury found that none of Google's implementation code was infringing, that isn't even an issue here, all of their code was sufficiently different, or was the same only because that was the only reasoanble or efficient way to do it (i.e. merger).
Clean room reverse engineering is also not the issue with the declaring code. It's the same because it has to be the same. No amount of "clean room" can change that, so it doesn't matter whether they disassembled the byte code from Oracle's compiled library, looked in the documentation, or looked in the source code. It's always going to be the same.
Alsup's original decision was not only technically accurate, it was logically sound and based on solid precedent. The CAFC decision overruling him contained logical fallacies, and apparently deliberate mistatement of fact and precedent at pretty much every turn.
He may not know what GNU is, or appreciate the joke, but he's nowhere near the clueless judge depicted in the article. And the menu analogy was lame.
Part of the problem in this court case is the poor explanations offered by the technical experts. What they should have said to explain it:
A programming language is like a human language. It defines the rules and syntax for constructing sentences for those wishing to speak the language or those wishing to understand the language.
A programming API is like a lexicon, or a vocabulary. In order to speak a language, you have to know what words it has available and what they mean. Without that, you cannot actually communicate anything using the language.
An API implementation is like a printed-and-bound dictionary. It offers a full explanation for the words in the lexicon, so people can make use of them. It is not the vocabulary itself, that is an intangible concept. It is merely one person's expression of the semantics underlying that vocabulary.
A dictionary can be covered by copyright.
A lexicon cannot.
An implementation of an API can be covered by copyright.
The API itself cannot.
Are lightbulb jokes, but they're all obsolete. Does anyone have any good LED lightbulb jokes?
And I still regard google as EVIL ever since they changed their motto to "All your attention are belong to us."
Freedom = (Meaningful - Coerced) Choice != (Speech | Beer^2), and sad sock puppets' bad mods avail them naught.
The number 5 would be hard to copyright, but any long enough number will do. Essentially that's all a digital file is: a large number. And these can be copyrighted.
Mods, why is this marked troll? It seems to be an honest position all the way to the end. Nothing really outrageous about it.
> The parts of the Java API that define the names and types of the various elements are the declarations, and there is only one way in Java to express them without changing the meaning and functional specifications for the API being expressed. Thus, Google's declarations are going to be almost identical to Oracle's, and that should not be infringing.
No, this does not hold. Nothing in the law guarantees that google is allowed to express the _exactly_ the same idea than oracle is using. In fact, the opposite is true -- it's explicitly illegal to copy large number of elements from a plot of a book, even if they didn't use exactly the same words to express it. Manual translations of the original to different form creates a derived work, instead of losing their copyright protection. And the current situation seems to be that they used exactly the same api definitions.
It's a strange development that people tend to utilize every alternative available to go towards the edge of what is allowed by copyright law. The default still is that those actions are illegal, and instead of trying to find loopholes in the law, people should just accept that the actions are simply illegal. Examining these situations shouldn't require a lawyer's degree -- the real problem is that people want to stretch the permissions they're given, instead of actually fixing the problem. Fixing it means that you simply do not have access to other people's technology when you implement your own technology. Why should google have _exactly the same_ technology than what oracle is using? It's important that every company is doing slightly different stuff, instead of just copying what other companies are doing.
If they want to use a copy of oracle's tech, they can always license the technology from oracle. But guess the tech was more difficult to create than they expected, if they didn't get licensing deal done for faforable enough terms.
To each any every one of you who claimed that jury duty was a waste of their time, effort, and for all of the other idiotic variations of not wanting to do their civic duty, this is what happens.
III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIII
Supreme Court is now stuck in an endless loop,
I heard that Linux does these in six seconds.
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
You're simply wrong. The statute explicitly says, and with the intent to exactly do that, allow copying the functional idea:
102(b) In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.
A plot is not functional. The elements in a plot are not essential parts of an "idea, procedure, process, system, method of operation, concept, principle, or discovery", so the copyright protection of the expression, the written words, extends to the plot.
This isn't some strange obscure loophole, it's a basic principle of copyright. Copyright is not supposed to protect functionality. APIs have been free to copy and adapt and enhance and extend since the IBM PC BIOS was first legally cloned.
If you want to protect function, get a patent. Otherwise, it's free to use and build upon.
The primary objective of copyright is not to reward the labor of authors, but "to promote the Progress of Science and useful Arts." ... To this end, copyright assures authors the right to their original expression, but encourages others to build freely upon the ideas and information conveyed by a work. ... This result is neither unfair nor unfortunate. It is the means by which copyright advances the progress of science and art.
Surly given the time and cost involved ...
Yep, definitely, Joe Six Pack is going to be surly after you've tried to teach him all that...
> APIs have been free to copy and adapt and enhance and extend since the IBM PC BIOS was first legally cloned.
This sounds like very dangerous idea. Cloning of PC BIOS most likely involved very accurate legal manovering, which normal companies simply do not have access to. This idea is clearly at the edge of what is allowed, and popularizing it to be something that everyone should be doing just sounds like dangerous for the people involved. Basically every person must ensure that the operations they're doing are legal, and going to the very edge of what is allowed, is simply very stupid idea. People should assume this stuff is simply illegal, even though there exists people who have managed to do it without getting sued.
Wouldn't explaining how an API works fall under fair use? You're not copy-pasting the API for use in your software product, and therefore not unfairly competing or stealing from the API vendor.
But the courts should decide if books explaining how APIs work are violating the copyright of the API vendor.
A spot reserved to write the date is not a creative work, it is merely something that is required for any cheque to be usable.
A spot for dates on cheques can be creative work and can only be protected by a utility patent, not something as weak as copyrights. This is about copyright infringement, or exact copying of somebody's original work without payment/licensing. /. is full of pirates who hate creative people and just want to steal their work without paying a dime.
... when that pool is obviously not your peer.
> This isn't some strange obscure loophole, it's a basic principle of copyright.
Well, the court paperwork explicitly rejected this idea, for the reason that api definitions are part of program source code, and thus covered by copyright. The exact quote is as follows:
"petitioner argued that theSSO constitutes aâoesystemâor âoemethod of operationâthat is ineligible for copyright protection under Section 102(b)of the Copyright Act."
"The court of appeals rejected that argument,ex-plaining that Section 102(b) âoerestate[s]*** the basic dichotomy between expression and idea.â"
"The court concluded that, for these purposes,computer code is âoeexpressionâ despite its functional character. "
people like you are the reason most people would gleefully execute all user-facing IT workers,
I don't work as an user-facing IT worker. I'm the IT security guy who works behind the scenes to make sure computers are updating properly and all software conforms to the baseline standard. Users who reboot the computer while I'm on it are the ones who complain to management and are shocked to get a verbal warning not to do that again. Corporate policy states that computers don't belong to users and users can't prevent technicians from working on the computers.
I hope Trump wins and puts you into camps.
If Trump ever releases his corporate policies for IT, I wouldn't be surprised to see identical language.
Now get get back to work computer janitor.
How productive would you be at work if people stopped cleaning up your shit?
I like the breakfast menu analogy better, as it's closer to what an API actually looks like and, usually, behaves. It's really just a list of things that trigger off actions. Those actions vary from restaurant to restaurant. The car analogy isn't quite as close, IMHO, as mechanically you are much closer to doing the work.
My Other Computer Is A Data General Nova III.
> Science and technology can't move forward if we don't allow ourselves to stand on the shoulders of giants.
You can just get a license to the work. People already are forgetting that it's possible to spend your money and buy a permission to use the underlying technology.
How else are the developers of the technology going to get their invested money back, if people just steal the technology, fill the market with copies of the tech, and then hide illegally obtained money to luxenburg?
This is only partially true. At its core, copyright is simply the right of exclusivity to control who may copy a work. In fact, one does naturally have this right of exclusivity if they do not ever share their work in the first place. After all, if nobody else has it, nobody else can copy it. Copyright suggests to the person it is being offered to that legally speaking, they would still have this exclusivity even after publishing (even if they do not any longer "naturally" possess it). Theoretically, this might encourage people who would otherwise be so concerned that people may copy their stuff without authorization that they would resort to self-censorship to publish their works anyways, and society could be enriched by them. Of course, that incentive only works to the extent that people voluntarily respect that law. Theoretically, the general public's incentive to respect copyright is supposed to come from the enrichment that the society receives from creators that may have otherwise not published at all, offering a continually diverse set of published works. If these incentives are not strong enough for either one party or the other, then copyright starts breaking down. This is where we seem to be at today, but I don't want to get into that too far.
Anyways, while copyright may not truly be any kind of natural right (although if you think about it, very few things really are), it *is* a kind of logical extension of something that could otherwise be an entirely natural right, but has been augmented to try and function in the real world.
File under 'M' for 'Manic ranting'
You make it sound as if Google had no choice but to copy the APIs, coz there's no other way. But the reality is, there are multiple ways to express the same ideas. For example, Java itself has two different APIs just for file access: the regular one is in the java.io.* package and the other API for files is called NIO. Clearly, there are multiple ways to express file and other APIs and Google could easily create their own API for file access.
But the reason they chose to copy Sun/Oracle's API could be because they wanted something that programmers were already familiar with and to free-ride on the success of the Java language + API. Creating their own API would be risky, expensive, time-consuming, and prone to failure as it has not been tested.
And yet "a jury of your peers" must surely demand some understanding of the domain of expertise and the issues being tried.
Absolutely not. The use of "facts" not presented as evidence is considered "bad" by the court system, there was no debate, no cross examination of the "expert" who provided the "fact" to the juror. Plus there is the technical problem that many "facts" are in fact "opinions", dearly loved and deeply held opinions that the holder can not imagine not being true.
I don't think the phrase originally meant "a bunch of perfectly average 'normals' too dumb or lacking in initiative to get out of jury service".
The original phrase had more to do with social class, a peasant having a jury of peasants not a jury of lords, and little to nothing to do with technical expertise, for example a blacksmith having a jury of blacksmiths. At best there was being of a sound mind and unbiased disposition. Perhaps unbiased implies not having a bunch of dearly held opinions in a relevant subject matter?
Lol you're such a cunt.
No, I'm an asshole. I wouldn't be working in IT if I wasn't.
And Schwarz's explanation that the acronym GNU stands for 'GNU is Not Unix' drew the following exchange: "The G part stands for GNU?" Alsup asked in disbelief. "Yes," said Schwartz on the stand. "That doesn't make any sense," said the 71-year-old Clinton appointee.
In follow-up news, Richard M. Stallman was served a subpoena to thoroughly explain the 'recursive' acronym, and additionally, to brief the jury on the facts of the case.
In an unusual exception, both the prosecution and defense agreed that popcorn would be provided free to the court, both parties, and spectators to the case.
Heil Environmental Industries Ltd. is a company that makes garbage collection trucks.
Exact copying? Not even close.
Substantial similarity so as to confuse the market
That is the legal standard. Thus Microsoft got away with stealing Windows from Mac, who got away with stealing from PARC, by making the "market" issue irrelevant
No, Google had no other way to express that particular API. Yes, there are plenty of different ways to do the same type of functions, but they would be different. Google is permitted to use that specific API.
Besides the quote from the Supreme Court above ("This result is neither unfair nor unfortunate. It is the means by which copyright advances the progress of science and art.") there's the CONTU report from which which the Ninth in Sega, and the Second in CAI, quote:
In some circumstances, even the exact set of commands used by the programmer is deemed functional rather than creative for purposes of copyright. "[W]hen specific instructions, even though previously copyrighted, are the only and essential means of accomplishing a given task, their later use by another will not amount to infringement."
Implementing a different API is not "accomplishing a given task". In particular, replacing the class files in the Oracle version of the library with class files compiled from Google's code would not accomplish the same task if the API was different.
This is how the courts and the Congress have shaped copyright law, and it's the way they intend it to work. The CAFC decision is an aberration, filled with mistatements, misapplication of precedent, and major logic failure.
You have no idea what an API is, do you?
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
> >They couldn't enter the market that oracle/sun built for themselves
> A market is not something you can build for yourself. You can only build artificial barriers for the others to enter, which is often illegal in a regulated market.
Why would hostile takeovers of companies markets be allowed? For normal large companies, it's extreamly important that they don't _accidentally_ enter markets which they don't have license paperwork in good condition. It's possible to do accidentally, and large companies know to avoid such problems. But in the current situation, it seems google is trying hostile takeover of sun/oracle market using oracle's own tech.... This kind of situations are exactly what copyright/patent laws are designed to solve.
> If Google could create an alternate API they would. Except they don't want to spend tens of millions and several years to come up with a new API and implementation.
I don't think this is the reason why google doesn't implement their custom api. They could create completely new api very easily. The real reason is that programmers will reject it because it doesn't provide the same functions than java standard library. The momentum is in java api's structure, the actual implementation issues are minor problems compared to building your own communities and popularity to the technologies in question.
Google's android is clearly freeriding on java's popularity. The reason is that everyone who has ever looked at android, will think that it's an implementation of java platform. They simply can't avoid this, because any programmer that looks into the technology will immediately regognize the structure of java platform in android technology. So the analysis is that they do need java license for that technology. It's amazing that they do not have a license, even though the tech is clearly available all over the world.
And then it may be up to Congress to change the law. I'd rather not have judges changing the law just to get a result I see as reasonable.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
There's another complication here. How much are regular Java programs interoperable with Android programs? If I were implementing a version of Java, I could claim that I need to copy the API to create my own compiler. I'd be on much shakier ground if I were writing a compiler for a new language and decided to use the Java API just for convenience. AIUI, Oracle is arguing that Google produced something that won't run Java programs, and therefore used it to make things more familiar rather than for interoperability.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
However, why did Google choose to use that API? Was it to allow Java software to run under Android, or was it to present a familiar interface to Android programmers? Oracle is arguing that Android is sufficiently different that Google could have designed its own API without losing functionality.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
Buying licenses is not going to work for Free/Open Source software. For that to thrive, there has to be some legal mechanism to allow use of the APIs.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
Both, but it doesn't matter. Copyright law doesn't protect functionality. That's what patent law is for.
Do you understand the difference between API documentation (e.g. javadoc in this case) and the API itself ?
Bingo Dictionary - Pragmatist, n. A myopic idealist.
Functionality is if I write a Java runtime to run Java programs on. I've got a really good case for doing that, which is really what the industry needs in copyright permissions. If I create a different language that's going to run on the JVM, that's functionality. If I create a different language that's not going to run on the JVM, the functionality question is much less clear.
The usual idea of functionality is whether I could write something different and still get the same functionality. In the case of a system that runs Java programs or runs on the JVM, I have to use the API as written. If I'm doing something different, I can get essentially the same functionality with a different API. Oracle is claiming that Google is not intending to run standard Java programs on Android, and is using Dalvik
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
The functionality, the "given task", is "run this Java source code".
If it can't do that, then it isn't the same functionality.
Precisely.
Oracle is arguing that there's enough difference between current Java programming and Android programming that the functionality argument fails. They claim that Google could have used different APIs without losing significant functionality, since programs for the Android use sufficiently different facilities.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
It doesn't have to reproduce all functionality. There's no such requirement. If I copy the entire API, make a drop-in replacement for Oracle's library, some parts of the source code must be the same for it to work, to have the same function. The expression is inseparable from the idea. Copying those elements is not infringement.
Once I (conceptually) do that, there's nothing that says I can't change my version, whether that's removing parts, changing parts, or adding parts. Copying those elements is not infringement, even if I don't copy all of them.
APIs have been held to be copyrightable. That means that, to copy without a license, you need to have a valid defense against infringement. You don't get to start by saying that copying an API is not infringement and doing whatever you like with it; you present your use and say why it isn't really infringing, typically by invoking an argument about functionality. If you had to copy the API to provide functionality, that's cool. If you did it for some other reason, such as not wanting to make your own, that isn't.
APIs are creative. To offer some service, the API designer must select which functions to provide, the names of the functions, and the parameters. If you and I were to design APIs for the same thing, we'd wind up with similar overall designs and different sets of functions, function names, and parameters. The functionality argument only comes in when the API is in use in some way, and there's a reason to be compatible with it.
Oracle is arguing that, since regular Java programs and Android programs aren't at all interchangeable, the API copying is for convenience, not functionality, and hence is infringing. Whether this is true is a question of fact, as far as the courts go, and I'm not going to say one way or another.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
APIs are copyright in one case. In other courts, it's the expression of an API, the source code, that's protected, not the actual API. Just as Google could reimplement the idea of a procedure to e.g. compare two character strings, or store a set of references to objects in a container, without infringing on that idea, the idea of how to invoke that procedure (call a method named java.lang.String.compareTo, passing two pointers to String, returning an integer) should also be able to be reimplemented without infringing.
If I said the way to invoke that was to call subroutine number 3246 instead of giving it a name, would you have a problem with that not being protected? Is it the names?
The only thing an API provides is functionality. An API is a functional idea. The source code is copyrighted. The functional idea is not supposed to be protected by copyright. It doesn't matter why you copy it, it's not protected, just as I can copy an algorithm (unless it's patented), for any reason I want.