Slashdot Mirror


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.

14 of 436 comments (clear)

  1. Re:"The G part stands for GNU?" by Plus1Entropy · · Score: 5, Insightful

    Honestly, I think we made our beds, and now we're being forced to sleep in them.

    --
    Only crack the nuts that crack. You don't put the ones that don't crack in the sack.
  2. Oh my god by NotSoHeavyD3 · · Score: 5, Insightful

    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.
    1. Re: Oh my god by ShanghaiBill · · Score: 5, Insightful

      I know what APIs are, and I couldn't figure out that menu 'explanation'.

      The "menu analogy" didn't make sense to me either. The power plug analogy was better, since (unlike a menu) that really is an interface. It lets you use power from any source (solar, wind, coal, nuke) to power any device (computer, TV, microwave oven). You can swap any source or device in-or-out as long as it adheres to the spec (analogous to the API).

      The power plug analogy also demonstrates why copyrights/patents on interfaces are a really bad idea. If everyone need a separate plug for every power source / device combination, then our walls would be covered with outlets, and you would need to hire an electrician every time you bought a new lamp.

    2. Re:Oh my god by roman_mir · · Score: 5, Interesting

      Or he could have thought about it for 10 minutes and said something like this:

      API is a silhouette, a contour, an outline of an object, but it is not an object itaelf, it is a promise that the object will provide functionality that the contour is hinting about.

      To copyright a contour while maybe possible should not penalize those, who want to provide their version of an object that is projecting the same contour. A contour of a woman's body is clearly recognizable but it does not say anything more than 'it is a woman'. A contour of a car promises that the object behind it is a car but the car itself with all of its parts cannot be seen.

      Applications depend on such contours to request the functionality of the objects behind the contours. To allow a company to put a lock on a contour would destroy ability of applications to use each other's functionality and would significantly and negatively impact the economy.

      To prevent others from projecting a promise of functionality by using an existing and well recognized description of that functionality through the means of these API object contours is to stop all development of alternative systems unless sanctioned by the current legally recognized owner of the specific object providing such functionality. But an outline of a system is not a system itself. An outline of a door is not a door yet it makes it clear that there is a door and it can be used.

      Should a particular door maker be able to prevent others from making doors that people can walk through because we recognize a rectangle on a wall as a passage, as a door regardless of the company that made the door?

      Do we want a single company to control all doors?

    3. Re:Oh my god by r0kk3rz · · Score: 5, Insightful

      ...and this is why so many people are mystified by computing, the people that understand it are really bad at analogies.

  3. Truly unprofessional headline and story by Anonymous Coward · · Score: 5, Insightful

    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.

    1. Re:Truly unprofessional headline and story by Anonymous Coward · · Score: 5, Informative

      I'm not sure the summary is accurate wrt to the article or if the articles writers are slanted, because there was praise for Alsup in Oracle v. Google (2012) for actually knowing how to program. Would argue that maybe the better interpretation of Alsup's questionings and responses were that the programmers and lawyers were dumbing down the explanations too much.

      https://tech.slashdot.org/comments.pl?sid=2887227&cid=40175735

      by gcnaddict ( 841664 ) on Thursday May 31, 2012 @10:17PM (#40175735)

      via c|net [cnet.com]:

      On many days, the San Francisco courtroom where he presided was more like a computer science classroom. Alsup acknowledged during the trial that he had learned about Java coding to better prepare for the case, and it showed. On a daily basis, he would deftly query the lawyers and expert witnesses on the structure, sequence, and organizations of APIs to assist the jury in understanding the key facets of the copyright phase of the trial.

      This is why I have respect for Judge Alsup. In order to apply the law in a complex engineering-related case, he worked to learn the subject matter in order to properly apply the law to the material. That's how I expect every Judge should apply the law rather than just sit and "trust the experts" per-se.

  4. Not wrong by Anonymous Coward · · Score: 5, Interesting

    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.

    1. Re: Not wrong by Anonymous Coward · · Score: 5, Insightful

      That's what expert witnesses are for. The judge also has the power to say that something doesn't make sense and ask questions. The problem here is that the judge is providing feedback and, instead of addressing the feedback, the judge is being treated like an idiot.

  5. Erm Guys... This Judge writes code.. by andydread · · Score: 5, Informative
    This judge is not clueless
    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?

  6. GNU is a recursive acronym by TerraFrost · · Score: 5, Interesting

    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.

  7. Re:"The G part stands for GNU?" by Beeftopia · · Score: 5, Insightful

    Recursion is not a simple concept to someone who has never heard "recursive case" and "base case" and "function". It's not a simple concept even to those who have. So, no snobbishness I think.

    They're like engineering jokes: "What do you get when you cross an elephant and a grape? Elephant grape sin theta." No one who doesn't know what a cross product is, is going to get that.

    This speaks to the weakness of the jury system. It worked well enough in agrarian times for simple concepts. But this is not a jury of (programming) peers. So they're not being judged by jury of their peers.

  8. Re:HS diploma who failed geometry by Ferocitus · · Score: 5, Funny

    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.

    How can you explain Microsoft's Win 10's strategy without referring to a shit sandwich?

    --
    USB, USB, USB!
  9. Re:"The G part stands for GNU?" by ShanghaiBill · · Score: 5, Funny

    They're like engineering jokes: "What do you get when you cross an elephant and a grape?

    What do you get when you cross a tsetse fly with a mountain climber?

    Nothing. You can't cross a vector with a scaler.