Slashdot Mirror


Google Developer Testifies That Java Memo Was Misinterpreted

benfrog writes with a piece that appeared in yesterday's Wall Street Journal about the in-progress legal battle between Oracle and Google over Java: "Ex-Sun and current Google employee Tim Lindholm testified that it was "not what he meant" when asked about the smoking gun email (included here (PDF)) that essentially said that Google needed to get a license for Java because all the alternatives 'suck[ed].' He went on in 'brief but tense testimony' to claim that his day-to-day involvement with Android was limited."

28 of 201 comments (clear)

  1. Liar liar by Anonymous Coward · · Score: 4, Funny

    Pants on fire.

    But we're on Google's side so we'll let it go.

    1. Re:Liar liar by shutdown+-p+now · · Score: 5, Insightful

      Because Oracle is on the other side.

  2. Oh come on by msobkow · · Score: 5, Insightful

    If he didn't mean they should negotiate a Java license with Sun, why did he say:

    ...we need to negotiate a license for Java under the terms we need.

    How you could possibly interpret that statement as meaning anything other than "we need to negotiate a license" is beyond me. I may not like Oracle's aggressiveness in pursuing the issue, but I can't read this email as being anything other than an acknowledgement that Google needs a license.

    Now don't get me wrong. Google could have later used the GPL version of Java safely, but they didn't have that option back then. Plus there's the question of whether you're allowed to use pieces of a GPL piece of software, such as the Dalvik compiler and core runtime with a Dalvik-compiled copy of the Java code for it's libraries and packages.

    I would contend that they're well within the GPL, provided that the Dalvik code was also released under the GPL. However, if the Dalvik core isn't under GPL, then they've got the issue of mixing GPL and non-GPL code to muddy the waters, and maybe that's the angle Oracle is playing.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:Oh come on by pla · · Score: 5, Insightful

      How you could possibly interpret that statement as meaning anything other than "we need to negotiate a license" is beyond me.

      "We need to buy shiny toy X" doesn't always, or (IMO) even usually, mean "we've already chewed the fingers off it, guess we need to pay for it now".

    2. Re:Oh come on by dgatwood · · Score: 5, Interesting

      If he didn't mean they should negotiate a Java license with Sun, why did he say:

      It seems likely that he meant that they should negotiate with Sun for a license. However, the most likely meaning of such a statement (when spoken or written by an engineer) is that it would be easier to get a quality product out the door in a timely manner if they licensed Java from Sun than if they wrote their own implementation, and thus, from an engineering perspective, they needed to do so. The powers that be chose to rewrite it instead of buying a license, therefore no license was needed from either a legal or a technical perspective. It is therefore downright silly to interpret such a statement from an engineer as implying that a license was legally necessary.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    3. Re:Oh come on by BillX · · Score: 5, Informative

      Looking at the various email threads, it reads to me like Google decided a Java-compatible platform was their best option, and licensing one from Sun (they already had one, called Java) was the easiest path to getting the job done. Another email in the exhibit mentions the possibility of clean-rooming their own Java-compatible platform, but basically saying it would be a giant PITA and not cost-effective vs. just licensing Sun's existing one. I don't see the Java license discussions as construing "proof of knowledge of infringement" (etc.), or belief that it was the only legal path forward, only that at least one guy believed it was the easiest path forward.

      --
      Caveat Emptor is not a business model.
    4. Re:Oh come on by julesh · · Score: 4, Insightful

      How you could possibly interpret that statement as meaning anything other than "we need to negotiate a license" is beyond me. I may not like Oracle's aggressiveness in pursuing the issue, but I can't read this email as being anything other than an acknowledgement that Google needs a license.

      Read the context prior to that. At the point that email was sent, Google's plan was to use the name Java in their marketing. Java was Sun's trademark, so of course they would have needed to licence it.

      They decided not to, however, instead hiding the connections between Android and Java in developer-oriented documentation, and being careful never to claim that Android implements Java in any way (it implements a system that is compatible with programs for the Java programming language, or some other such nonsense, that is always careful not to suggest any Sun/Oracle endorsement of the system).

  3. Fairly plausible by pla · · Score: 5, Insightful

    Reading the email linked by the FP, I would call his claim fairly plausible - I wouldn't take him to have meant "gee, we've infringed the hell out of it, we need to get legal ASAP", but rather "Can you please just buy the best option for us so we can move on and stop the games?"

    Honestly, something like that exact discussion comes up on a monthly basis where I work, and some shyster could probably find examples of me saying substantially the same thing in my emails. And I don't give two shakes of a rat's ass about whether or not my employer wants to stay legal on the licensing side - If they don't mind me using a copy of Windows registered to Razor1911, no skin off my back (and hell, good ammo for me if things get ugly).

  4. Re:Most vital lesson learnt: Hire the right person by thaylin · · Score: 5, Funny

    Of course you have never written a message like that, he used proper grammar in his emails. 8)

    --
    When you cant win, ad hominem.
  5. Nice foresight by ghn · · Score: 5, Informative
    On Fri, Feb 20, 2009 at 7:59AM, Dave Sobota wrote:

    2. Can you spell out the risk of us relying on Sun for support in more detail? I thought Java was largely opensourced anyway -- so I don't understand why we'd be so worried if Sun went bankrupt, was sold to an unfriendly company or just decided to act erratically with respect to Java. Is it that we are concerned about the parts that are not opensourced (e.g., test suite) --that Sun might jack up the license fees or just stop licensing those altogether?

    p29 of the exhibit

  6. Re:Most vital lesson learnt: Hire the right person by Anonymous Coward · · Score: 3, Insightful

    If I am working for the human resource department of Google, I will fire that Mr. Lindholm long ago

    Where the hell have you been working that HR get to choose who to fire? That's really not how it works.

  7. Re:Pretty clear to me by ghn · · Score: 3, Informative

    But they could not work out an agreement with sun to obtain a licence with the terms and price tag they needed. So they did not call their implementation 'java', thus, not infringing on the trademark.
    The trial is about patent infringement, not trademarks..

  8. This e-mail was years after Google started Android by Chibi+Merrow · · Score: 5, Insightful

    No matter what he meant, it shouldn't matter. Oracle is trying to use the e-mail to prove "Google knew ahead of time they were in the wrong!" when in fact this e-mail was written AFTER Oracle bought Sun and was murmuring about lawsuits. It's also an unsent draft of an e-mail written by a Google employee who wasn't working on Android! Wow!

    I guess if I want to screw over my company in the future, I know how to do it now... Incriminating e-mail drafts!

    --
    Maxim: People cannot follow directions.
    Increases in truth directly with the length of time spent explaining them
  9. Re:Pretty clear to me by symbolset · · Score: 4, Informative

    It's about both patent and copyright. They're down to only one patent though. The actual copyright is minimal, so Oracle's trying to make the silly argument that they have a copyright on the API. Not only is such a thing impossible, but they can't produce a "work" that's infringed nor an exemplar of a reproduction.

    I'm going to agree with the grandparent. One employee urging the company buy something to solve a certain problem is not proof the company stole it. If the company decides to achieve its goals in a different way strategically because the object of their desire is not for sale (which is the case here) this also doesn't mean that they stole it.

    --
    Help stamp out iliturcy.
  10. Re:Obvious implementation by sco08y · · Score: 4, Informative

    That "copied" code is a joke.

    If you have the function prototype per the java doc and you test the limit cases to see what exceptions are thrown, how else can you implement that array range check in a non-trivial way?

    That's just lawyer bullshit.

    My first thought, too, but it's a private method, not implementing any API.

    What's funny is that they're highlighting this trivial function while inadvertently showing that Android uses TimSort, whereas the Java standard library which, according to the docs, uses a tuned quicksort, adapted from Jon L. Bentley and M. Douglas McIlroy's "Engineering a Sort Function".

  11. He meant a *driver's* license by larry+bagina · · Score: 4, Funny

    You know, go down to the DMV and get a driver's license so android could drive one of those google cars. In the country Java (note the capitalization), not for the JAVA SDK.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  12. He ain't a lawyer by sirwired · · Score: 4, Informative

    I read it as: Whatever kind of license we need to run Android, we should get one. As somebody who was not, himself, actually involved in any kind of licensing negotiations, laws, etc., he didn't have the least flipping clue WHAT that might entail.

    Imagine my boss seeing emacs for the first time and saying "Holy $hit! this emacs is awesome! SirWired, go buy whatever we need to run it." That isn't any kind of admission that running emacs requires paying somebody; just a statement that he wants it.

    Google's position is that no license from Sun was in fact needed, and that Eric Lindstrom was not the person that had anything to do with that determination

  13. Re:Most vital lesson learnt: Hire the right person by Anonymous Coward · · Score: 3, Informative

    So you wouldn't call one of the authors of the original Java Virtual Machine spec a person who you would hire? Look at the top of this document:
    http://docs.oracle.com/javase/specs/jvms/se7/html/index.html

  14. Erm by ShooterNeo · · Score: 3, Insightful

    NOTHING is free. Everything takes time and money to create. Now, for various reasons, people give software away...but this is a massive corporation producing software worth billions of dollars, and a key part of it depends on software that was developed at a cost of millions of dollars.

    So a reasonable few million bucks to Oracle for their trouble seems fair.

  15. Re:This e-mail was years after Google started Andr by Chibi+Merrow · · Score: 5, Informative

    Actually they are trying to use the email to show that Google were knowingly breaching the license, not that google knew ahead of time that they were in the wrong.

    I don't think I understand the subtle difference in what I said and what you said... So let me try to be clear by pretending to know what I'm talking about for a second: Oracle is trying to use the e-mail to show evidence of WILLFUL INFRINGEMENT.

    And it could be evidence of that, except: 1) it was written after Oracle started threatening, 2) it was written AFTER Sun's CEO publicly congratulated Google on releasing Android and promised Sun would support the Android platform 3) it was written by someone in Google not working on Android 4) it was saved as a draft but not sent.

    Oracle are dicks, but that is only a mild improvement on the twats that are google.

    Are you trying to say Oracle is less evil than Google? Are you at all familiar with Oracle?

    Honestly even if Google is in the wrong here (which I strongly disagree with), I think it's vitally important Oracle lose this case, as the legal theory they are trying to push (that public APIs are subject to copyright and licensing) is absolute INSANITY and would be the death knell to a large percentage of the software industry.

    Though it would make developing on proprietary systems significantly more painful than Free/Open systems like Linux, so that would make some people around here very happy...

    --
    Maxim: People cannot follow directions.
    Increases in truth directly with the length of time spent explaining them
  16. Re:Most vital lesson learnt: Hire the right person by pla · · Score: 4, Insightful

    If there is any lesson to be learnt from this trial it gonna be this - Hire the right person [...snip...] I mean, what qualification that Mr. Lindholm has on legal stuffs ?

    Google did not hire Mr. Lindholm to work as a lawyer. Would you also expect your janitors to know how to code? Your delivery drivers to reconcile AP? Your controller to weld deck plates?


    How can an ex-Sun employee, currently employed by Google, write an email saying things like "Google need a license for Java" ?

    Because non-lawyers can still put two and two together to come up with four. Because the average employee frequently needs to make recommendations within their own domain of knowledge that have implications outside that domain. Because IT people in particular don't generally give a shit about what HR thinks, and HR would already fire us in a heartbeat if the company could live without us.

    Or more accurately - Because someone asked.

  17. Re:Pretty clear to me by symbolset · · Score: 3

    It's a bigger deal than that because the Java APIs are clearly derivative of C and C++ libraries. Oracle DB and SQL is clearly derivative of other work. Which means if Oracle wins this one they've effectively commited suicide. All their IP would belong to somebody else.

    --
    Help stamp out iliturcy.
  18. Re:Most vital lesson learnt: Hire the right person by hairyfeet · · Score: 3, Insightful

    Actually I would say it should be looked upon as a more fundamental question which is this: Should email be treated as a letter, or as a text message?

    The problem with treating emails like a letter is simply people don't think about emails like they do about a letter, probably because it is so trivial to send. With a letter one has to take the time and consolidate their thoughts, write them down, fold it up, put in the envelope etc, whereas with emails they are treated with no more thought most of the time than a LOLCat.

    I just have to wonder how many times companies will be bitchslapped by emails like this before they either simply don't allow emails or have them disposed of quickly. because unless you can somehow get your employees to treat emails with the gravitas of a formal letter they will just keep biting you right in the ass.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  19. Re:Let me google that for you by 93+Escort+Wagon · · Score: 4, Funny

    You think a great man like Larry Page dirties his fingers with a computer keyboard?

    He has Siri look it up for him.

    --
    #DeleteChrome
  20. Re:Most vital lesson learnt: Hire the right person by julesh · · Score: 4, Insightful

    No. But you would expect employees (well, maybe except for janitors) to understand the implications in the current legal climate, and refrain from putting things so bluntly as "we're clearly violating these patents and must get a license", even in internal email - unless they are explicitly asked to express their legal opinion. At least, that sort of thing has been part of on-boarding training in pretty much every place I've worked in the last eight years.

    Except that's not what he says. Patents are not, at any point, mentioned in the memo. The memo expresses a desire to use the Java trademark in marketing Android. It is well-known that Sun required licensing of the Java Technology Compatibility Kit and a successful pass of its tests before it would allow you to use the Java trademark in this way, so the license stated as required (a license for the TCK software, not a patent license) would most definitely have been required IF google had proceeded with the plan as it was described in that memo. They did not proceed with this plan, however, instead deciding to distance themselves from Java, make their virtual machine incompatible with the Java virtual machine (although providing tools supporting automated translation between the two formats), and not use the Java trademark in any of their marketing material. So it is unclear what relevance a (correct) statement about the licensing terms on the Java trademark has on a court case about a system that does not use that trademark. This so-called "smoking gun" is just misdirection on Oracle's part.

  21. Re:This e-mail was years after Google started Andr by Shoe+Puppet · · Score: 3, Insightful

    Unlike Microsoft, Google doesn't claim that their platform is compatible with the JVM. Just as C can be compiled for x86 or ARM, Java can now be compiled for JVM and Dalvik and nobody claims they are bytecode-compatible.

    --
    (+1, Disagree)
  22. Re:Skipped the best part. by julesh · · Score: 3, Informative

    Actually, the license discussed in the email is for TCK, which is a tool for testing and certifying that Java implementations correctly implement the Java standard.

  23. Re:Most vital lesson learnt: Hire the right person by moss45 · · Score: 3, Informative

    Your being an idiot aside, this was an unsent DRAFT email.

    It is not just a draft. Oracle ARE using the drafts as evidence, but the final email also included the licensing language. The reason Oracle had to use the drafts was because the original email was at one point argued to be privileged information. It was found not to be and the final email is considered evidence.