





Google Developer Testifies That Java Memo Was Misinterpreted 201
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."
Nice foresight (Score:5, Informative)
p29 of the exhibit
Re:Pretty clear to me (Score:3, Informative)
The trial is about patent infringement, not trademarks..
Re:Pretty clear to me (Score:5, 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.
Re:Obvious implementation (Score:5, 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 [oracle.com], uses a tuned quicksort, adapted from Jon L. Bentley and M. Douglas McIlroy's "Engineering a Sort Function".
He ain't a lawyer (Score:5, 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
Re:Most vital lesson learnt: Hire the right person (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
Re:This e-mail was years after Google started Andr (Score:5, Informative)
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.
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...
Re:Oh come on (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.
Re:Skipped the best part. (Score:4, 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.
Re:Most vital lesson learnt: Hire the right person (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.
Re:This e-mail was years after Google started Andr (Score:2, Informative)
You'll probably get furious then if you'd see this [gnu.org] or this [excelsior-usa.com]. Those bastards are even worse than Google - they compile our pretty and portable .jars to completely non-crossplatform machine code! How dare they.
Java programming language != Java platform. There's no "contract" that any jar will run on any platform using Java programming language - go try running Java EE application on a Java-enabled phone or Bluray's BD-J applet on your PC.
And yes, MS was bitchslapped because they claimed to implement standard, compatible Java SE implementation while introducing incompatiblities. Google claims to implement NOT any of Snoracle's Java platforms, but a new runtime using Java programming language.
You can now proceed to remove your foot from your mouth.