Slashdot Mirror


Judge Blasts Oracle's Attempt To Overturn Pro-Google Jury Verdict (arstechnica.com)

Joe Mullin, reporting for Ars Technica: Google successfully made its case to a jury last month that its use of Java APIs in Android was "fair use," and the verdict rejected Oracle's claim that the mobile system infringed its copyrights. After Google argued its case, though, Oracle filed a motion arguing that the judge should decide as a matter of law that fair use didn't cover it. In the wake of the jury's pro-Google verdict, Oracle's motion was its last hope of a trial victory. It didn't happen; US District Judge William Alsup shot down the motion on Wednesday. The same order also denied Google's motion making similar arguments, filed at the close of trial but before the jury's verdict. Alsup's stinging order [PDF], which rejects Oracle's argument [PDF] on every front, hardly comes as a surprise. But the document provides the first insights as to what Oracle might bring up in an appeal proceeding, which the company has said it will pursue. In the order, Alsup defends how he ran the trial. The evidence and instructions presented to the jury were a mix of mandates from the appeals court, which overruled Alsup on the key issue of API copyrightability, and modifications urged by both sides' lawyers.

106 comments

  1. Who are we rooting for today? by mi · · Score: 2, Insightful

    I forgot, is it Google or Oracle? Which multi-billion dollar corporation needs our sympathy, cheers, and support today?

    --
    In Soviet Washington the swamp drains you.
    1. Re:Who are we rooting for today? by Anonymous Coward · · Score: 5, Insightful

      It's more of an Aliens vs. Predator situation. Whoever wins, we lose.

    2. Re:Who are we rooting for today? by Anonymous Coward · · Score: 2, Insightful

      Never Oracle.

    3. Re:Who are we rooting for today? by HiThere · · Score: 5, Insightful

      Oracle is never on the side of right. This is so true that if they do something that you thought was right, you should think again and try to decide whether they are being deceitful, or whether you were wrong to thing it was the right thing to do.

      Google is sometimes a good guy. You can't use their actions as any guide to what proper behavior is. So they are less trustworthy than Oracle.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    4. Re:Who are we rooting for today? by spacepimp · · Score: 1

      Seriously... Why bother thinking about the importance of what was being argued/judged? Lets hang our hats on corporate entities and pretend that either of them care about us. If these were two much smaller companies, the importance would be the same...

    5. Re:Who are we rooting for today? by Tony+Isaac · · Score: 5, Informative

      Whichever one happens to be on the side of sanity.

      In this case, Google was arguing that an API shouldn't be copyrightable. For anyone who understands what an API is, this makes total sense.

      If I want to make an after-market alternator for a Honda car, I can do so by creating my own device that has the right size pulley, screw threads, electrical output, and so on. This absolutely is "fair use." In the same way, the API is the spec for the functionality behind it. I should be able to make an after-market part that meets those specs, without infringing on any copyrights.

      Because Google was on the right side of the issue, I root for Google in this case. But if the roles were reversed, I would root for Oracle just as quickly.

    6. Re:Who are we rooting for today? by Anonymous Coward · · Score: 1

      I was rooting for the inability to copyright functional aspects of a thing, such as the round shape of a wheel, the + in a phillips head screw, the + in a phillips head screwdriver, or the operation of the screwdriver on the screw, which we define here bool tighten(PhillipsScrew screw); bool loosen(PhillipsScrew screw); implements IAnythingCanBeAHammer { bool hit(Nail nail); }.

      Sadly thats not what we got our ruling on, probably because a ruling that interfaces are functional and not creative would upset a lot of lawyers, of which Google has plenty, so keeping it a fair use courtroom defense makes sure the lawyers keep getting paid. It also allows Google to argue that using their interfaces is not fair use when the time comes for them to be on the plaintiff's side.

    7. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Except that this trail was about FAIR USE of the copyrighted API SSO.
      In the previous trial Google successfully challenged the copyright-ability of the API and won. Oracle appealed and had that overturned (in my opinion erroneously) so this trial was whether or not Google's use was a fair use of the Java APIs.

    8. Re:Who are we rooting for today? by spacepimp · · Score: 0

      Yes... Hillary Clinton clearly fights the slings and arrows of corporate influence to be a protector of us citizens from copyright extension.

    9. Re:Who are we rooting for today? by myowntrueself · · Score: 1

      I forgot, is it Google or Oracle? Which multi-billion dollar corporation needs our sympathy, cheers, and support today?

      Who ever roots for Oracle? Oh, that'd be that One Rich Asshole CEO Larry Ellison.

      --
      In the free world the media isn't government run; the government is media run.
    10. Re:Who are we rooting for today? by Mr.+Gus · · Score: 5, Insightful

      Google doesn't need our sympathy--Oracle needs our antipathy. The people behind Oracles side of the case are sociopaths attempting to do something that will set a precedent that is extremely negative for technological progress in American society. Once set, it could extend beyond the country as part of our continual series of copyright treaties, making Oracle responsible for doing serious damage to human society as a whole. They're monsters who should be locked up.

      Nobody seriously should care whether Google has to pay a million or even a billion dollars to some company, but they should care about the dangerous precedent Oracle was trying to set.

    11. Re:Who are we rooting for today? by Aighearach · · Score: 3, Funny

      If you find yourself thinking Oracle is as right as a stopped clock, (twice a day) just remember to check the fine print. It probably really means you pay double.

    12. Re:Who are we rooting for today? by KiloByte · · Score: 1

      Both are ruled by Republicans.

      Oh yeah, especially that evil Google is putting its weight to let Trump win.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    13. Re:Who are we rooting for today? by mrchaotica · · Score: 3, Informative

      Sadly thats not what we got our ruling on, probably because a ruling that interfaces are functional and not creative would upset a lot of lawyers, of which Google has plenty

      Everything after "probably because..." is wrong. In fact, Google did argue that interfaces are functional and not creative, and prevailed in that argument -- in the previous trial. Then Oracle appealed, and the appeals court stupidly overturned it and then sent the case back to the lower court. This trial was forced to be conducted around the assumption that interfaces are creative.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    14. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      The detail you are correcting makes no difference whatsoever to the point of the post you are responding to - Google was on the right side of *this case*.

      Whether they're on the right side of any other case can be evaluated on a case-by-case basis.

    15. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Alsup FTW!

    16. Re:Who are we rooting for today? by MightyMartian · · Score: 4, Insightful

      It's not about which one of them cares about us, but rather being pragmatic. There are many situations in which the enemy of my enemy is my friend. If Oracle is successful in its claims that APIs can be locked down, there's a world of hurt coming in the US, as any organization or individual that has replicated the function call list of any library (including kernels) could be viewed as having infringed on the original creator of that API. By that I mean just the call list and/or symbol tables, not any actual code.

      In this case, Google is fighting an important fight that we should all hope it is successful in. Tomorrow it could be fighting a fight we disagree with.

      To simply mindlessly support a company is the worst kind of fanboism, as mindlessly attacking a company's every move is just pointless contrarianism. Even Microsoft fights some fights I agree with, even if I think Redmond is run by some of the most loathsome individuals in the tech history.

      Oracle, sadly, is a company whose positions almost always seem to fly in the face of reason, ethics and fair play, but it's at least theoretically possible that some day they may be on the right side of a battle. I dunno, maybe they don't like North Carolina gender bathroom laws or something.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    17. Re:Who are we rooting for today? by immortalcrab · · Score: 1

      I understand APIs, I've designed them and I believe they are copyright worthy independently from implementation. Good API design is hard work, requires expertise to do it, is not trivial and does guide implementation.

    18. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Oracle doesn't need our antipathy. Safra Catz and Larry Ellison need out antipathy. Don't dilute it by referring to a faceless corporation. The leaders are the dirt bags.

    19. Re:Who are we rooting for today? by immortalcrab · · Score: 1

      You are right according to the current legal ethos the functional aspects or things aren't copyright-able but PATENTABLE, and we surely don't want that, so copyright is a good compromise.

    20. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      I understand APIs, I've designed them and I believe they are copyright worthy independently from implementation.

      Most of the world disagrees with you, as do I, and this judge, and Google, and ... well, you get my point.

      Good API design is hard work, requires expertise to do it, is not trivial and does guide implementation.

      Partly true, and completely beside the point.

      Implementation is guided only so far as what the input and output (and possibly effect) should be.

      As long as the specific piece is not completely trivial (thus negating all of your points by definition) then the implementation need not at all be guided.

    21. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Black Lives Matter, bro.

      What the fuck do blacks create, other than ghettos and welfare babies? Are you incapable of doing anything other than destroy what the white man has built?

    22. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      I disagree, API's are not copyright worthy.

    23. Re:Who are we rooting for today? by Anonymous Coward · · Score: 1

      If Oracle claimed that water flowed downhill, I would lose my faith in physics.

    24. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      I understand APIs, I've designed them and I believe they are copyright worthy independently from implementation. Good API design is hard work, requires expertise to do it, is not trivial and does guide implementation.

      Just because something is hard does not mean it is automatically worthy of copyright protection.

    25. Re: Who are we rooting for today? by Anonymous Coward · · Score: 0

      Good paraphrasing of Half-Life 2, there. Dr Been would be proud.

    26. Re:Who are we rooting for today? by immortalcrab · · Score: 1

      I understand APIs, I've designed them and I believe they are copyright worthy independently from implementation.

      Most of the world disagrees with you, as do I, and this judge, and Google, and ... well, you get my point.

      Good API design is hard work, requires expertise to do it, is not trivial and does guide implementation.

      Partly true, and completely beside the point.

      Implementation is guided only so far as what the input and output (and possibly effect) should be.

      As long as the specific piece is not completely trivial (thus negating all of your points by definition) then the implementation need not at all be guided.

      So SQL and Prolog code isn't copyright worthy either, cause you only define sets and sentences and the actual algorithm it is inferred by a runtime environment? Defining output, input and effect does indeed guide the implementation in a way no functional requirement would. Your last quote is a non sequitur because I never trivialized implementation I just pointed out that API design is not trivial.

    27. Re:Who are we rooting for today? by Agripa · · Score: 1

      Good API design is hard work, ...

      Sweat of the brow was rejected in the US as a criteria for copyright.

    28. Re:Who are we rooting for today? by Xtifr · · Score: 1

      Good API design is hard work, requires expertise to do it, is not trivial and does guide implementation.

      None of which is a reason for something to be copyrightable! If hard work alone were copyrightable, every ditch digger in the world would be owed royalties from every ditch they've dug. If requires-expertise made something copyrightable, then I should be able to claim copyright on Poe's "The Raven" because I can recite it from memory. If guides-implementation made something copyrightable, then again, those ditch diggers should get royalties from the plumbers who laid pipe in those ditches.

      In the case of designing a good API, most of the hard work comes from figuring out what people are likely to expect, and matching that as closely as possible. That's pretty much the opposite of "creativity", which is what gives something copyrightability. Figuring out what people are likely to expect and matching that as closely as possible falls under the category of "scenes a faire", which is explicitly excluded from copyrightability.

      A sufficiently creative API might be copyrightable, but it would also almost certainly be a horrible API, not a good one, since by definition it wouldn't be using the obvious, expected choices.

    29. Re:Who are we rooting for today? by spacepimp · · Score: 1

      I was being sarcastic, and failed at it... To put it more directly: Root for the outcome not the company. Personally I side with Google in this, like I sided with IBM in IBM v SCO. I still wonder if there is a Ballmer connection in the back rooms to encourage these actions and put FUD back into open source, only this time against Android. However they already lost the battle, MS has no phone/mobile OS. But that too is just greed, which I believe is the single entity which motivates Oracle.

    30. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Putting together a phone book is a hell of alot of hard work too, but they are not copyrightable.

      So just because you put in work, does not mean the law gives a shit, pipsqueak.

    31. Re:Who are we rooting for today? by fufufang · · Score: 1

      Oracle seems to be less innovative than Google. Let's root for Google.

    32. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Yep, Google only recently turned evil.

      Oracle has always been evil!

    33. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      Hillary takes their money (lecture fees) and then sets about writing legislation to pin their ears back.

      Win - Win.

      Do you really think that any GOP president will prevent, among other worse things, the greedheads from pushing through the US Senate the currently-bottled-up legislation that WEAKENS the "mens rea"* standard for financial crimes? For those of you with short memories, the "excuse" given by the Feds for not locking up the banksters after 2008 was that they read all that incriminating email but couldn't find "mens rea". First, that's a sick joke. Second, now the GOP wants to water down even THAT standard.

      Nobody at that level is clean; it's a matter or relative cleanliness and you take your choice, as South Park said it, between a giant douche and a turd sandwich.

      * a guilty mind; a guilty or wrongful purpose; a criminal intent. Guilty knowledge and wilfulness.

      Why do I post anon coward? Because I work in this industry, poke big sticks in their eyes as I do so, and want to remain employed/employable.

    34. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      He's probably an Apple zealot who is still seething that anyone else was allowed to make smartphones.

    35. Re: Who are we rooting for today? by Maritz · · Score: 1

      You lost the case. Deal with it.

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
    36. Re:Who are we rooting for today? by david_thornley · · Score: 1

      The ruling was on the basis of existing law. APIs are creative works that are fixed in a tangible form, and are therefore copyrightable. An API is not purely functional when it's created, since there's typically many ways to make one. Asking for a different court ruling is asking for judicial activism. Writing to your representatives in Congress and telling them why APIs should not be copyrightable would be much more productive.

      The idea that APIs are copyrightable, but may be used as we normally use them due to fair use, does work.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    37. Re:Who are we rooting for today? by Anonymous Coward · · Score: 0

      as others have said up thread, if you think Oracle is on the right side of an issue, then there is either skulduggery afoot, or you are on the wrong side of the issue. Oracle is ALWAYS evil, it's in their corporate charter, you know how Google has "don't be evil"? Oracle has "don't NOT be evil"

  2. Copyrighting APIs by Anonymous Coward · · Score: 5, Interesting

    I've never heard of a stupider idea. How about I think about all the functionality that could be implemented by someone somewhere, then write these extremely easy one line expectations. I'll make a huge number of them as well such that all the arguments you'd expect to pass in for that type of functionality are covered.

    Now that I've claimed copyright, the ability of a random person to use program a computer to do something useful has been taken away from them. That, and I barely had to do any actual work. The functionality hasn't even been implemented. Isn't the US legal system great?

    1. Re:Copyrighting APIs by epiphani · · Score: 5, Insightful

      While I agree with your premise - read the judgement. It's actually pretty impressive. The judge clearly took the time to learn some programming and some java. It's a very well thought out, and clearly well informed judgement. For a judge to dive this deeply into the issue gives me some hope for some of the other idiocy of the legal framework around software.

      --
      .
    2. Re:Copyrighting APIs by mrchaotica · · Score: 4, Interesting

      This judgement is from the judge that previously ruled that APIs were not copyrightable. It's the incompetent appeals court who made the fucked-up ruling.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    3. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      Exactly. They still got it all wrong. APIs ought not be copyrightable, it makes no sense, it is a catastrophe for software makers , whether there are sometimes fair use exceptions or not.

      Let's all start to write gigantic books with APIs for just about everything, and make the arguments "optional, if the language supports it", or auto-generate all permutations of arguments. Then sue everyone on earth.

    4. Re:Copyrighting APIs by Fire_Wraith · · Score: 1

      It's also interesting to note that in the interest of getting a better understanding of the issues involved in the case, the judge (William Alsup) took the time to learn to program in Java. If only more judges (or politicians for that matter) could be bothered to be this tech savvy!

      http://radar.oreilly.com/2012/...

    5. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      I've never heard of a stupider idea.

      It is not a stupid idea. It is a brilliant idea if you can get away with it. I think the word you are looking for is 'evil' .

    6. Re: Copyrighting APIs by Anonymous Coward · · Score: 0

      The lawyers around the world encourage you to get started ASAP!

    7. Re:Copyrighting APIs by DickBreath · · Score: 1

      Who would have ever thought that re-implementing an API would be copyright infringement.

      Question: how many times has the Standard C Library API been implemented? How many different implementations?

      Another thought . . .

      Who owns the copyright on the API to the Standard C Library? Oh, wait. He's dead Jim.

      But did he assign the copyright rights to anyone? Nope. Why? Because at that time nobody ever believe we would live in a world insane enough for anyone to even hint that copyright should apply to APIs.

      So his estate must own the copyright to the Standard C Library API. Oh, I think I smell money and lawsuits! Hey, Lawyers, look over here!

      --

      I'll see your senator, and I'll raise you two judges.
    8. Re:Copyrighting APIs by phantomfive · · Score: 1

      And this ruling by the judge is aimed at the appellate court, it's not a 'blast' at Oracle, that's just a hype headline. The judge ruled against Oracle, very calmly, on the first page. It then goes on to talk directly to the appellate court ("Since an appeal is promised, however, it may be of assistance to leave a few important observations.").

      The judge spends several pages explaining why APIs should be fair use. He explains that textbooks reproduce exactly the same APIs. He says that if someone tried to use Java without those APIs, then it would be like using a typewriter where the keys aren't QWERTY.

      The appellate court nearly ruled in favor of Oracle on fair use in the last appeal, and Judge Alsup didn't like their ruling at all, so here he is trying to make an argument in favor of all APIs being fair use. He makes a very good argument, but now Oracle's lawyers will have a chance to counter argue, and the appellate court agreed with them before.

      There's so much hype around this case, but because Google didn't use a clean-room implementation, a ruling against them wouldn't necessarily be bad for the rest of us. Google was sloppy.

      --
      "First they came for the slanderers and i said nothing."
    9. Re:Copyrighting APIs by mrchaotica · · Score: 1

      He says that if someone tried to use Java without those APIs, then it would be like using a typewriter where the keys aren't QWERTY.

      That's an unfortunate analogy. It would be more like using a typewriter where the keys are in the Cryillic alphabet.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    10. Re:Copyrighting APIs by phantomfive · · Score: 1

      Maybe. I would look at the C# and Java comparison: when I first switched from Java to C#, it was different, but I kind of knew what I was looking for, and I was able to find it easily enough. I quickly gained 'muscle memory' in C#. So similarly, if I switched to a random keyboard layout, it would be a pain at first, but I would know what I was looking for, and find it easily enough. Whereas with a cyrillic alphabet, it would like switching to Forth or something.

      --
      "First they came for the slanderers and i said nothing."
    11. Re:Copyrighting APIs by bain_online · · Score: 1
      Actually copyright does not work like patents.

      You have to prove that the accused actually did wilful act of copying the copyrighted material (or at least accuse can to disprove it). If accused can prove that they came up with it completely on their own they are not infringing a copyright. Which can be easily done by sharing a git log of a particular software project showing from start to end one wrote the entire thing and its evolution to its current form (if it indeed was developed in house and completely free of copyright infringements).

      In Google Vs Oracle google admitted to copying from get go. Their argument was they thought it was OK to do so.

      Also to claim damages you will need proof of lost income, which in your case will be zero or the penalties will be really small ones.

      --
      BAIN http://www.devslashzero.com
    12. Re: Copyrighting APIs by Anonymous Coward · · Score: 0

      except his works were work-for-hire. ATT could then pull the Oracle maneuver...

    13. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      I think the word you are looking for is 'evil' .

      I agree. Protecting your code from people who will copy it without compensating you is truly ... evil. Blessed are those that copy APIs without payment in the name of technological progress.

    14. Re:Copyrighting APIs by tricorn · · Score: 1

      No, clean room wouldn't have made a difference. Google in fact was found to not infringe on any of the "implementation code", it was the declarations that were found by the appeals court to infringe. There is no way to write those declarations another way without changing the API, so a clean room would not give any different result. It was the API itself that was found to be protected, so no matter how you try to do it, the information needed by the clean room is "dirty". A clean room implementation is impossible given the CAFC decision.

    15. Re:Copyrighting APIs by phantomfive · · Score: 1

      Google in fact was found to not infringe on any of the "implementation code",

      That's not true actually, they were found (by the jury) to have infringed on the rangeCheck code, and the appellate court let the finding stand. The clean room technique ensures that you only copy the bare minimum to reach your purpose, which is an important consideration under factor number three of fair use.

      What about the other fair use factors? 1, 2 and 4? For example, with fair-use factor number 1, Google's use was for-profit, whereas most open source projects are not. Google's use also wasn't for purposes of interoperability, which is the major reason for wanting to copy an API (if they had done a good job being interoperable, Sun would have happily given them a license, since that's what Sun wanted in the first place).

      --
      "First they came for the slanderers and i said nothing."
    16. Re: Copyrighting APIs by Anonymous Coward · · Score: 0

      Except works for hire do not attract copyright.

    17. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      The C Standard Library is a published international standard (ISO/IEC 9899) and part of the POSIX specification, so they are intended to be re-implemented. That doesn't necessarily prevent them from being copyrighted.

      However, Caldera open-sourced Unix up to V7 & 32V under the BSD license, so it would be hard to argue any kind of copyright violation on the C library headers.

    18. Re:Copyrighting APIs by tricorn · · Score: 1

      True, they did accidentally copy one method, and Oracle agreed to accept $0 in damages.

      Clean room is how you avoid infringement entirely, in which case fair use isn't even brought up. In this case, the CAFC made the whole process of clean room implementation impossible anyway.

      Google is indeed for profit, however giving away the code (including source code) at no cost isn't particularly indicative of commercial use and exploitation. A company donating money to education can deduct it from their taxes even though it generates commercially valuable good will or even mind share and future customers. Plenty of open source is sold, and even more is used for commercial purposes.

      It most certainly was for interoperability, otherwise there was no reason to use it at all. There are plenty of Java libraries that work fine with just those 37 packages, and interoperability with developer's skills is also something a jury might well find relevant - Oracle doesn't own their skills and training.

      The reason Google didn't take a license was that Sun would only license JavaME for use on a mobile device (which, by the way, was also not interoperable with JavaSE).

      Google's use was also transformative. They selected out a useful subset of the Java API, rewrote all of the actual implementation and documentation (97% of the code), then wrote a whole lot more more new APIs using the old APIs in new ways; together the old APIs and new APIs presented a lot of new capabilities that seem to have done a lot better than JavaME in the smartphone area.

      The nature of the copyrighted work was highly functional, a factor strongly in favor of fair use. Oracle even proved it, just change a single name by a single character and the whole thing won't work.

      The total amount that was actually used from Oracle's API code was very tiny, less than 0.2%, just the names and relationships between those names, in 37 packages out of 166, so maybe 20% of 3% of 22%. That's 20 (scattered) words out of 10,000.

      As for market impact, Oracle had OpenJDK available for free as well, licensed under GPLv2+CE. Anyone who wanted to use JavaSE could already get it for free - and if the additional parts of the API were that important to people in any significant number, OpenJDK would be much more desirable than Google's truncated implementation.

    19. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      > Clean room is how you avoid infringement entirely, in which case fair use isn't even brought up.

      Clean room is how you traditionally avoid infringement, because you create a new implementation but use the existing API.

      The big issue with this case was the copyright status of APIs. If APIs are copyrightable, you can't even do clean-room because your new implementation becomes a derivative work of the API.

      The problem now is that APIs have been ruled copyrightable, and Google's use of them judged "fair use." Fair use has to be decided on a case-by-case basis, so any and all clean-room techniques are now much riskier. You can't rely on the law to protect your use of the API. Your fair use defense may not succeed.

    20. Re:Copyrighting APIs by phantomfive · · Score: 1
      Well, actually your comment shows some of the best understanding I've read of the topic on Slashdot. So good job.

      The total amount that was actually used from Oracle's API code was very tiny, less than 0.2%,

      The size is mostly irrelevant though. In one case (Harper & Row v. Nation Enterprises) someone copied 400 words out of a 200,000 word book (the supreme court ruled against them). As one judge said, "you can't escape guilt by showing how much you didn't copy." You have to look at the importance of the copying, and whether they used more than necessary for the purpose.

      Google's use was also transformative. They selected out a useful subset of the Java API, rewrote all of the actual implementation and documentation (97% of the code), then wrote a whole lot more more new APIs

      That's not really what is meant by transformative. Here Google's approach was to say, "Before we did this, Java couldn't be used on mobile. We created a new work that allowed people to use Java on mobile." Oracle's counter-argument was to show phones that did have J2SE on mobile (SavaJe, Blackberry).

      The nature of the copyrighted work was highly functional, a factor strongly in favor of fair use

      Oracle's counter to this was to quote Google's own expert witness, Joshua Bloch, who said, "Writing a program is very much a creative process," and more (see here and here). The appellate court also pointed out that just because cod is functional, that doesn't prevent it from being creative (otherwise basically no code could be copyrighted, since it's all functional).

      It most certainly was for interoperability, otherwise there was no reason to use it at all.

      It didn't pass the Sun Java test suite (if it had, there wouldn't have been a problem). Google didn't push this argument as much as I expected them to in court, I'm not sure why.

      As for market impact, Oracle had OpenJDK available for free as well, licensed under GPLv2+CE.

      The court is supposed to look at potential income lost here. If your argument were correct, it would mean the GPL is meaningless because anyone could claim the market value was zero. You can't just take code and not follow the license.

      Google is indeed for profit, however giving away the code (including source code) at no cost isn't particularly indicative of commercial use and exploitation.

      That's Google's argument. Oracle counter-argued that Google made plenty of money from Android, and showed quotes from internal emails saying that if Google hadn't used Java, they wouldn't have been able to bring Android to market in time, for example, "It is widely believed by that if an open platform is not introduced in the next few years then Microsoft will own the programmable handset platform" and "we have two options: 1) Abandon our work and adopt MSFT C# language, or 2) Do Java anyway and defend our decision, perhaps making enemies along the way."

      In this case, the CAFC made the whole process of clean room implementation impossible anyway.

      I don't know why you think this. clean room is a technique to ensure that no more was copied than necessary, which would weigh favorably on fair use factor three (or at least prevent it from weighing negatively, since the amount copied is at best a neutral factor).

      --
      "First they came for the slanderers and i said nothing."
    21. Re:Copyrighting APIs by DickBreath · · Score: 1

      Caldera would seem to be irrelevant. Someone wrote the header files long before Caldera or the Canopy group ever existed. Who wrote the original header files would be the moment copyright existed. (Although I believe copyright law was revised, IIRC, in 1978? And that is when copyright became automatic at the moment of creation?) I'm not sure how publishing a copyrighted API, or even a complete implementation of the API would make copyright go away. Especially in the eyes of copyright owners and courts today where copyright seems to trump everything else, free speech, due process, the 4th, 5th and other constitutional amendments, and maybe even international law.

      --

      I'll see your senator, and I'll raise you two judges.
    22. Re:Copyrighting APIs by Maritz · · Score: 1

      You lost. Tough shit. Suck it the fuck up. :D

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
    23. Re:Copyrighting APIs by tricorn · · Score: 1

      The size is mostly irrelevant though. In one case (Harper & Row v. Nation Enterprises) someone copied 400 words out of a 200,000 word book (the supreme court ruled against them). As one judge said, "you can't escape guilt by showing how much you didn't copy." You have to look at the importance of the copying, and whether they used more than necessary for the purpose.

      As a general principle, yes, but all the factors are weighed. It was the same percentage, but it was stand-alone paragraphs and sentences, not scattered individual names that don't stand on their own. They also were a much larger portion of the infringing work, it was not functional, it wasn't yet published, it reduced demand for the original.

      That's not really what is meant by transformative. Here Google's approach was to say, "Before we did this, Java couldn't be used on mobile. We created a new work that allowed people to use Java on mobile." Oracle's counter-argument was to show phones that did have J2SE on mobile (SavaJe, Blackberry).

      Oracle wouldn't allow Google to license JavaSE for a phone.

      It was transformative because they created entirely new implementation code, and used the existing API in new ways. That it wasn't transformative in the same way a parody is transformative is, I submit, entirely due to the highly functional nature of the work.

      Oracle's counter to this was to quote Google's own expert witness, Joshua Bloch, who said, "Writing a program is very much a creative process." [...] The appellate court also pointed out that just because cod is functional, that doesn't prevent it from being creative (otherwise basically no code could be copyrighted, since it's all functional).

      102(b) doesn't say "unless it's really creative". The actual expression (the source code) doesn't lose protection unless there's merger - which was the case here because any changes to the actual declarations would change the functionality. 97% of the code retained protection, which is why Google had to write their own.

      Another way to say it is that, given the API specification, there is no creativity required to turn it into the declaring code. For example, I offer the javap program.

      The court is supposed to look at potential income lost here. If your argument were correct, it would mean the GPL is meaningless because anyone could claim the market value was zero. You can't just take code and not follow the license.

      No, the GPL has requirements other than money, and no one has ever thought it restricted reimpkementing an API. It works just fine, and many open source projects have reimplemented APIs without license.

      OpenJDK was released with the Classpath exception. Oracle had already reduced any potential income with OpenJDK, having two free alternatives with almost identical licensing requirements wouldn't have hurt the market more than having just OpenJDK.

      I don't know why you think this. clean room is a technique to ensure that no more was copied than necessary, which would weigh favorably on fair use factor three (or at least prevent it from weighing negatively, since the amount copied is at best a neutral factor).

      A clean room requires functional specifications, the Java API itself, to be passed in. That API was ruled to be protected, thus there'd be nothing to pass in that was clean. If they passed it in anyway, they would have produced exactly the same code that was found infringing (except maybe without the rangeCheck oops, which didn't make any difference). It was already the case that no more than was necessary was copied.

    24. Re:Copyrighting APIs by phantomfive · · Score: 1

      They also were a much larger portion of the infringing work, it was not functional........etc

      You are misunderstanding the fair-use factor 3, the amount copied. That isn't a positive defense, at best it is neutral: Google can say "We copied no more than necessary." But Oracle will try to argue that they did copy more than necessary.

      The actual expression (the source code) doesn't lose protection unless there's merger - which was the case here

      No, that was Google's idea, but the appellate court explained why it is wrong, see here starting on page 30. In brief, when considering merger for copyright protection, you need to consider the options available to Sun when they originally wrote Java: there were plenty of ways they could have written any of those APIs.

      It was transformative because they created entirely new implementation code, and used the existing API in new ways.

      Indeed, and Google absolutely owns the copyright on the new implementation code, that isn't even in dispute.
      --
      The point I'm trying to make here isn't so much to decide whether Google should lose or not, I honestly don't care if one company pays billions to another. My point is that even if Google loses, there is plenty of reason that the ruling would not apply to most other open source projects, like Wine or Samba. There are clear differences between what Samba is doing and what Google did.

      --
      "First they came for the slanderers and i said nothing."
    25. Re:Copyrighting APIs by tricorn · · Score: 1

      You are misunderstanding the fair-use factor 3, the amount copied. That isn't a positive defense, at best it is neutral: Google can say "We copied no more than necessary." But Oracle will try to argue that they did copy more than necessary.

      None of them are positive defenses. All are factors that weigh more or less in favor of fair use or against it. They are also not exhaustive, the jury can use other factors as well. Read the jury instructions.

      Amount used (in comparison to the infringed work) is an important factor. The amount of copied material compared to the rest of the infringing work is also a factor, it goes to "the purpose and character of use" - if most of your work is just copied material, it weight against fair use. In Sega, the entire ROM was copied many times in it's entirety, even downloaded from the Internet, for an explicitly commercial use, yet they won on fair use with those two factors completely against them. One factor was that none of the protected material actually ended up in the finished product, other than a very small piece of code that was challenged on trademark but not copyright (and Sega lost on that as well). The other factor was the use and purpose of the copying.

      The Java API is clearly HIGHLY functional, and Google clearly copied the absolute minimum required to use it. The only copied material is the names and the relationships between the names, and changing a single character of any of those names would cause that portion of the API, and quite possibly the whole system, to completely fail. Hard to get more functional than that.

      Indeed, rather than show that the API was "the heart" of Android, Oracle's demonstration served to show how functional it is (especially since ANY section of code removed from Android, whether from the API or anywhere else, would also make it fail).

      The "nature of the copyrighted work" is clearly functional. You don't decide you want to replace the API in your project because you're tired of looking at this one and would like something fresh and new. You don't buy a product that uses Java inside for the artfully selected names like java.net.HttpURLConnection.setChunkedStreamingMode(), and if all the names were changed to AAAAA AAAAB AAAAC, etc. it would be just as functional, except it would be hard to write code for (so, again, the names are functional).

      It may take creativity to create it, but the work is functional, and the purpose for copying it is for the function.

      In brief, when considering merger for copyright protection, you need to consider the options available to Sun when they originally wrote Java: there were plenty of ways they could have written any of those APIs.

      The CAFC confused merger with scènes à faire. Merger is independent of point of view, it either is or it isn't.

      The API is an abstraction, it is an idea, protection is not supposed to "extend" to it. The expression is indeed copyrighted, but the idea expressed is not protected.

      The CAFC said that the "idea" was "an API", but that isn't what is expressed by the source code. The source code expresses a very specific API, the Java API. That is the "idea" that is not protected, whether you call it a process, a system, or a method of operation, 102(b) says the idea is not protected.

      Look at Baker v Selden or Bikram, the idea was not "an accounting system" or "a sequence of yoga poses" the way the CAFC would have you believe. In Bikram the Ninth completely rejected that the idea of "the Sequence" could be protected even though there were any number of ways it could have been created. Bikram was just about the idea being used, but once you have the ruling that the idea is not protected, merger can come into play. For example, expressing the Sequence as a simple list of each of the 26 poses by name would not be protected expression, as almost any expres

    26. Re:Copyrighting APIs by phantomfive · · Score: 1

      The CAFC confused merger with scènes à faire.

      I don't think so lol. Now you're just saying stupid stuff. Take a nap, think on it, and come back tomorrow with a fresh mind.

      --
      "First they came for the slanderers and i said nothing."
    27. Re:Copyrighting APIs by Anonymous Coward · · Score: 0

      It doesn't make copyright go away. It means you have an irrevocable license to the copyrighted material in question.

      It might be difficult to prove that you copied your "stdio.h" from a non-free version rather than modifying a free version.

  3. Is Oracle using SCO's law firm? by Anonymous Coward · · Score: 1
    Future headline

    "On October 1, 2028, following the judge in the case ruling against the last remaining claims, Oracle's suit against Alphabet(formerly Google) was dismissed with prejudice; Oracle then filed an appeal later that month"

    1. Re:Is Oracle using SCO's law firm? by phantomfive · · Score: 5, Informative

      Is Oracle using SCO's law firm?

      Yes, actually, Same law firm.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:Is Oracle using SCO's law firm? by DickBreath · · Score: 1

      Oracle just got slapped by the same Judge Alsup who smacked down SCO. BTW, SCO vs IBM started in March 6, 2003 is still ongoing, in a walking zombie sort of way.

      --

      I'll see your senator, and I'll raise you two judges.
    3. Re:Is Oracle using SCO's law firm? by evolutionary · · Score: 1

      LOL. And funny enough SCO is no more if my memory serves. Those who don't know their history..

      --
      "Imagination is more important than knowledge" - Einstein
    4. Re:Is Oracle using SCO's law firm? by tricorn · · Score: 1

      There are several judges involved in the SCO litigation, none of them Judge Alsup. It's not even the same Circuit.

      Alsup is Ninth Circuit in California, SCO v IBM and Novell are in Tenth Circuit in Utah.

  4. We're rooting against Evil by Anonymous Coward · · Score: 2, Insightful

    We're rooting for technological progress, so that means that everyone has to root for APIs to not be granted exclusive monopolies by the government. That means you should be on Google's side and it doesn't matter if either side happens to be rich.

    What Oracle is doing seems dangerous to me. The last they they should want are judges (or anyone else) thinking about this. Asking judges to reconsider Fair Use is a very bad idea, because the more someone understands the issue, the more likely that they'll realize: "you're right, Fair Use doesn't make much sense."

    It was an error to call it Fair Use, because it was a grevious error to even rule that an API could possibly be covered by copyright at all. The very nature of an API is that two entities speak it, so government misusing The People's power to grant a monopoly on a form of communication is absurd. Government does not need to grant monopolies in order to incentivize people to establish means of communicating with one another. That is a form of "the progress of the arts and useful sciences" which already incentivizes itself.

    The more people think about this, the more likely this error will be spotted by someone able to do something about it. (All three branches of the government could get involved in this to varying degrees; Oracle is lucky that only one branch is finding them so contemptuous so far.) Oracle won this case by advancing the cause of evil, even if they didn't get their money.

    Oracle: if you truly value injustice, unfairess, theft, technological retardation and stagnation, and want to help remove incentives for developers to create things, then you need to STFU immediately, because you're risking the loss of all your progress. Be happy with the damage that you have already done. It won't last, but you have have hurt everyone (Google almost doesn't matter in the larger context) for now, so you should be grateful.

    1. Re:We're rooting against Evil by immortalcrab · · Score: 1

      The problem is that Oracle didn't sue because Google used the APIs but because they re-implemented them, they used a fairly good design and redone it, but the design was copyrighted and it was copyright worthy. No one is saying that using an API is copyright violation, but this was never the issue.

    2. Re:We're rooting against Evil by Anonymous Coward · · Score: 0

      The design isn't copyrighted, Oracle CLAIMS it's copyrighted, and it's not copyright worthy, you and Oracle CLAIM it is worthy.

      None of which make the claims TRUE.

    3. Re:We're rooting against Evil by Maritz · · Score: 1

      No one is saying that using an API is copyright violation, but this was never the issue.

      I suspect Oracle not getting any money is your main problem with this? They used the patronising, emotional bullshit approach and it backfired spectacularly. lol.

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
  5. Cutting through the legal muckety-muck by SkyLeach · · Score: 1

    At the core of the argument is the irreducibility problem. APIs combine high-level wrappers around functional pre-requisites dictated by the way computers operate on information. Most of these concepts are just semantic wrappers around set operations or popular methodologies. Examples for this are the terms 'threading' and 'multiprocessing' surrounding algorithms for scheduling, messaging and the distribution of resources at fixed offsets, 'database' around a separate organized data retrieval system (even IBM Sterling is called an XML database, although it's more of an XML REST API on top of DB2).

    During community development, the names for API libraries are often built from micro-memes (ideas disseminated through a development group as semantic hooks to link together discussions).

    An API doesn't solve a problem, it builds an INTERFACE that has been reduced as much as possible (for usability) to the absolute minimum exchange of information necessary to execute an algorithm. Attempting to declare intellectual property ownership over the format of an API is, simply put, a giant greased slippery slope.

    Let's consider this as a symmetry experiment by swapping the IP owner out with another IP owner, such as the public domain. If we do this, then we should also be able to assume that public domain information that is used in proprietary IP requires that the IP become public domain. Solutions from mathematicians that are public domain (published in journals but accredited to them) would therefore mean that if the algorithm is used in a solution then by extension the algorithm is public domain and any API interface to the implementation is also public domain. That is to say, IP patents would all become null and void. Copyrights would apply, but only for distribution and marketing purposes.

    In Python one has collections and in Java one has collections, but essentially the APIs are just common semantics around very similar ways of handling sets of information and performing combinatorics with that information.

    This all comes down to the 14th amendment and the concept of equal protection. Build a solution, not a business plan of extortion that depends on sophistry and inherent lack of understanding among the lawyers and judges. Once one cuts through the semantics, we're really talking about the fact that IP patents are centered around a concept of 'first to market so we own the whole market' rather than true innovation.

    And we wondered while the publish it now, make it work later trend is getting worse?

    --
    My $0.02 will always be worth more than your â0.02, so :-p
  6. True. Mod parent up! by Anonymous Coward · · Score: 1

    Oracle and Microsoft are having a contest to see who can be most evil.

    1. Re:True. Mod parent up! by Anonymous Coward · · Score: 0, Troll

      Oracle and Microsoft are having a contest to see who can be most evil.

      Oracle and Microsoft make money by selling software.

      Google makes money by selling your privacy.

      As bad and Oracle and Microsoft may be, their fundamental business isn't inherently evil.

      Google, on the other hand...

    2. Re:True. Mod parent up! by Anonymous Coward · · Score: 0

      As bad and Oracle and Microsoft may be, their fundamental business isn't inherently evil.

      I see you've never done business with Oracle.

    3. Re:True. Mod parent up! by Anonymous Coward · · Score: 0

      All hail Larry, Prince of Darkness.

    4. Re:True. Mod parent up! by Anonymous Coward · · Score: 0

      Why do so many people misunderstand Google's business model. They don't sell your privacy, they keep your private information to themselves and sell your eyeballs. Your private information is far too valuable to Google for them to just sell it.

    5. Re:True. Mod parent up! by Anonymous Coward · · Score: 0

      as I understand it that came about as they were trying to implement an oracle database in hell to keep track of the damned, as these things usually go, the ultimate evil ended up swallowing the devil...

  7. Gore's lawyer by Anonymous Coward · · Score: 0

    Same one who worked for Gore in Gore vs Bush in the 2000 election.

    So does this mean he is a good lawyer or a bad one?

    1. Re:Gore's lawyer by Anonymous Coward · · Score: 0

      >good lawyer

      I'm sorry, I don't understand the words that are coming out of your mouth. Isn't that like saying something is a delicious pile of shit?

  8. Re:I have a much much better solution by MightyMartian · · Score: 1

    And portability will die. This isn't 1950 anymore, and heck, even in 1950 they understood the need for higher level languages.

    As it is, Google is moving away from Dalvik, but what hopefully will come of this is that company's can't expect to attack people who use their function names and symbol tables as infringers. I'd prefer it if APIs weren't copyrightable, but I suppose protecting them under fair use is nearly as good.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  9. Only is not by immortalcrab · · Score: 1

    Look I know Oracle is a company that doesn't raise a lot of sympathy for totally understandable reasons (litigiousness, overpricing, monopolistic behavior, you name it). But the APIs were never released by Sun to be open sourced even if they were permissive, and you all know that even when implementing an API is hard work, designing it is also hard work; I would argue that is half the work. Java APIs are very robust and comprehensive so the design wasn't at all trivial and the names and interfaces are work that is protected by intellectual property laws, and Oracle is the lawful owner of that intellectual property. I don't like Oracle, and I understand that asking for compensation is a dick move, but a lawful dick move that they were entitled to. I don't understand why all people are supporting Google on this, specially the open source people as this undermines the very provisions of licensed software that protect open source licenses; and I know android is a great way to monetize your software writing skills, and that Oracle is a big bully and I know that open source is copyrighted only because is the only way to keep it free in our legal environment but I don't think this is good news. I only see two big (and fairly evil) companies playing with the legal system and the worst outcome becoming a reality.

    1. Re:Only is not by Anonymous Coward · · Score: 0

      Moron...

    2. Re:Only is not by Anonymous Coward · · Score: 0

      Hey chaps
        I just patented a system intended to covey a meaning and to be used for writing by the use of letters in groups called words(tm) and the method and use of those to produce sentences
      you all owe me $$$$

    3. Re:Only is not by Maritz · · Score: 1

      You speak as someone who either (a) loves Oracle or (b) wants to utterly paralyse progress and innovation in software. Maybe both, I guess that also works? APIs being ruled copyrightable was insanity in the first place. This ruling merely limits the impact of that insanity for now.

      --
      I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.
  10. Ghost of Justice Scalia by Steve1952 · · Score: 1

    Pure applesauce and Jiggery-pokery! This trial came back to the jury because the higher court demanded it. If the creators and everyone else in the industry thinking that something is fair use isn't fair use, then what is?

  11. I was kinda hoping Oracle would win by Solandri · · Score: 1

    Just so Intel and AMD could sue them for everything they had for their software "violating" the copyrights on the x86 and AMD64 instruction sets. Unlike trademarks, you don't have to defend your copyrights to retain them. So Intel and AMD could sue Oracle, and only Oracle, for copyright infringement.

    I see it as similar to the Chinese artificial islands thing. You can argue and fight with the idiot for decades about why he's wrong and shouldn't do what he's trying to do, or you can just let him have his way, allowing him to self-destruct from the consequences, then you can revert back to the common sense approach. In China's case, let them have their way and declare that artificial islands expand territorial limits. Then every other country on Earth can start building artificial islands just outside mainland China's 200 nm territorial limit. Since territorial limits from different countries are determined by the half-way point, that would reduce China's 200nm limit to about 100nm. Then you build another artificial island at 100nm, reducing their limit to 50nm. And so on until the only seas China can claim extend out just 12 nm from their mainland.

  12. Judge William Alsup by Anonymous Coward · · Score: 0

    Judge William Alsup for Supreme Court!

  13. Why Oracle should win its Java copyright case... by amberdalan · · Score: 1

    I thought the this article brought up some salient points.....

    www.theregister.co.uk/2016/06/02/google_oracle_comment/

  14. Re:Why Oracle should win its Java copyright case.. by immortalcrab · · Score: 1

    Yes, this is just about right. I won't be the devils advocate, Oracle is a nasty litigious company, but this time they were LEGALLY entitle to their bullying. The outcome does in fact debilitate free software licenses cause now any big company can say "Hey, the code structure is the same but we changed the variable names, see? fair use!"

  15. I am so right! by Anonymous Coward · · Score: 0

    The appeals court reversed Alsop on the issue of the law, and so Alsop rigged the retrial by ignoring the initial charges and trying something else in order to attempt to reassert his decision. The appeals court will reverse him on the law again and smack him with something.

  16. Why Oracle filed this motion ... by Anonymous Coward · · Score: 0

    Whether you are for or against Oracle, everyone in this discussion seems to ignore the fact that Oracle _had to_ file this "Rule 50" motion in order just to _preserve_ their right to appeal since federal circuit appellate courts often refuse to hear arguments on appeal if they are not backed up by a "rule 50" motion at the original trial. Rule 50 motions (a.k.a. Judgment as a Matter of Law) basically just say that based on the case file the opposing party, Google in this case, has presented insufficient evidence to reasonably support its case.

    I would not want to be Oracle trying to find a foot to stand on in this quagmire of a pit they have dug for themselves, but while they fish around for something to grab a hold on, I cannot fault their legal team for filing a motion that they would be _remiss_ for not filing. The oracle legal team were just doing their job ... no matter how easy it was for the judge to "blast" (i.e. shoot down). Oracle as we have previously seen, has a "never say die" policy in courtroom battles, and while the verdict regarding "copyrightability" in the previous trial in 2012 seemed like a "slam dunk", they did manage to find an appellate court ruling to overturn that verdict. I can imagine their legal machine is on lock-down this time again to maintain their track record in overturning judgments they do not like. It would be premature to count them out yet on the verdict of "fair use".

  17. Just because you are partisan by Anonymous Coward · · Score: 0

    doesn't mean we must all be. Some of us actually look at the case itself rather than the "names" attached to it.

    Try it some time. Try NOT being an asshole bigot.

    And work out whether you think it's right APIs should be copyrighted and restricted by license, which will let you know which fucking side you're on.

    Just a thought. Try one of those yourself some time.

  18. The judge did an outstanding job by Anonymous Coward · · Score: 0

    For a lawyer, he did a good job of understanding the technical issues and applying this understanding in a consistent legal framework.

    His 20 page summary is worth reading

    http://arstechnica.com/wp-content/uploads/2016/06/order.denying.motions.pdf

    Couldn't ask for better.

  19. Re:I have a much much better solution by Anonymous Coward · · Score: 0

    Portability? Tell me then, why isn't there just one open/libreOffice, usable across all platforms straight from the archive? The only portable language I have seen is http.

    No, for the real stuff, statically linked Assembly solves all your problems. Hardware issues will just have to sort themselves out. In the meantime malware can't spread very easily. Speed and security, these are good things that need not be compromised for convenience.

  20. Re:Why Oracle should win its Java copyright case.. by Maritz · · Score: 1

    "Hey, the code structure is the same but we changed the variable names, see? fair use!"

    All you've done there is demonstrate, clearly, that you don't understand what is going on.

    --
    I do not want your cheap brainburning drugs. They are useless for work. And I am a working man today.