The quoted exchange is between Judge Alsup and Oracle's counsel, David Boies, and concerns the issue of what damages Oracle intends to seek in phase 3 of this trial (phase 1: copyright liability; phase 2: patent liability; phase 3: damages). The jury hung on the major copyright claims and the judge has yet to rule on the ultimate question whether the 37 Java API packages at issue are even protectible by copyright. Oracle proved infringement concerning the nine lines of code constituting rangeCheck and the judge held as a matter of law that Google had infringed respecting a couple of test files that were subsequently removed from Android. In this context, under applicable law, Oracle may elect to get statutory damages of $150K for each of the infringements or it may elect to go after what are known as "infringer's profits" - meaning that it would ask the jury to award it damages measured by profits made by Google on account of the infringing acts. Mr. Boies is telling the judge that Oracle wants to go for infringer's profits "as a matter of principle" and the judge is telling him, in effect, that he is astounded that Oracle would be prepared to make a claim for a billion dollars (or some other very large number) based essentially on nine lines of code among the tens of millions of lines of code in Android and a few test files. Mr. Boies strains to offer various rationales for how Oracle might prove damages of this type, mostly tied to the idea that Google gained in time to market for its Android product by relying on the infringing materials. The judge basically tells him that this position is ridiculous and that he cannot believe that an attorney of Mr. Boies's stature would even make it (at one point, he notes that Oracle is trying to make a "federal case" out of this and, catching himself, says (I paraphrase here), "oops, this is a federal case . . . well, seeks to make a bigger federal case out of it than it is"). (The Groklaw report on this exchange is worth reading and even fun in spots - it may be found here: http://www.groklaw.net/article.php?story=20120515120106322#U...)

This exchange highlights the rather unfavorable position that Oracle finds itself in on the copyright issues. It has won nothing of significance and stands to get very little from the jury on these issues. Concerning the broader claims on which the jury hung, it still faces a potent objection from Google that it cannot assert copyright violations based on the 37 API packages owing to defects in how the Java program was registered with the copyright office. It also faces the risk that the judge or a court of appeals will hold that APIs are not copyrightable.

A word on this last item: Much as the developer community believes very strongly that APIs should not be copyrightable, the Ninth Circuit law that is binding on this judge (beginning with Johnson Controls in 1989) is not particularly favorable in that it provides that software programs are to be analyzed item-by-item on the facts of each particular case to determine whether any particular component is protectible expression versus an unprotectible idea, function, system, or method of operation (this is in stark contrast to the First Circuit, which held that judges could make categorical judgments that certain components are functional by nature and hence unprotectible by copyright (as opposed to patent), as the menu structure was held to be many years ago in the Lotus/Borland case. Google is arguing the issue categorically ("APIs are inherently unprotectible under copyright law") but this makes for a tough sell in a jurisdiction where the appellate authority has said that such issues cannot be categorically determined. Google has alternative arguments, the main one tied to a leading Ninth Circuit case (Sega) that Google argues enables copying of functional elements of any program needed to ensure compatability. But, in my view, astute as this judge is, he will be bound to apply the fact-specific approach, making it tough for him to adopt Google's strongest argument and thus significantly reducing the prospects for a definitive ruling from the judge along the lines sought by Google (of course, this might come on appeal, where the court is free to reshape its earlier precedents in light of modern-day realities in the software world).

Source of my problems:

  design issues               5%
  architecture constraints    5%
  language shortcomings       1%
  mental blocks               5%
  personal time management    4%
  personal energy             5%
  communication with others  75%

I waste more time just trying to figure out what others are trying to say, sometimes in person and by voice, but mostly in writing. For most emails, I have to click "reply" or call back simply because what you're trying to tell me is so unclear. I think the last time I received a written specification I could actually work from was in 2002.

This isn't a problem of education, country of origin, or any other demographic: almost everyone sucks at writing. It's a real problem.

I suppose the best antidote to poor writing is more writing, especially on-line. Don't be bashful because as OP says, your readers won't be.

Thanks OP for the one "please" post this week that everyone can benefit from. (Did I just end that sentence with a preposition? Need more practice.)