Slashdot Mirror


Google Asks Supreme Court To Rule On When Code Can Be Copyrighted (theverge.com)

Google is asking the Supreme Court to make the final call in its infamous dispute with Oracle. "Today, the company announced it has filed a petition with the Court, asking the justices to determine the boundaries of copyright law in code," reports The Verge. From the report: The case dates back to 2010, when Oracle first accused Google of improperly using elements of Oracle's Java programming language to build Android. Oracle said that Google's use of Java application programing interfaces was a violation of copyright law. Google has responded that APIs are too fundamental to programming to be copyrighted. The case has led to two jury trials, and several rulings have doled out wins and losses to both companies over the course of eight years. Last year, a favorable Oracle decision set Google up to potentially lose billions of dollars.

Google asked for a Supreme Court hearing on the case in 2014, but the Court rejected the request at the time. The company says new issues are now at play, and is asking the Court to decide whether software interfaces can be copyrighted, and whether using them to build something new constitutes fair use under the law. In its new petition to the Supreme Court, Google says the case is not only important to copyright law, but has "sheer practical importance," as it centers around two touchstones of computing: Google's Android and Oracle's Java. The Court's intervention could alter the future of software, the company argues.

203 comments

  1. Fingers Crossed! by oldgraybeard · · Score: 2

    Lets hope the special interests and patent trolls don't get the court to screw up!

    Just my 2 cents ;)

    1. Re: Fingers Crossed! by Anonymous Coward · · Score: 0, Flamebait

      Still butthurt because you lost the election and we got two conservatives and probably a third on the Supreme Court by 2020. God I love the fact that you are being denied the very thing you want.

    2. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      Gorsuch: bring it!
      Kavanaugh: oh, its brung bitch!

    3. Re:Fingers Crossed! by Areyoukiddingme · · Score: 5, Interesting

      Good joke. As if Gorsuch and Kavanaugh are going to vote against corporate interests.

      It's Google v Oracle. There's a megacorporation on both sides of the courtroom. The Supreme Court is going to vote against someone's corporate interest, if they grant the writ at all.

      Google had better have been eloquent beyond all measure. Their lawyers have been working on this writ of certiorari since before October. If they fail to convince the Supreme Court to grant a hearing, it's all over and Oracle wins and software as an industry basically ends, swallowed by lawyers.

      For those playing along at home, if the last ruling in Oracle's favor stands, Novell essentially owns the Linux kernel. The Linux kernel reimplements the UNIX kernel API. If the ruling by the blithering idiots in the Court of Appeals is allowed to stand, that's illegal without a license. Novell's lawyers would have to write a license to allow Linux to continue to exist. All of the standard system libraries, especially things like libc, would become embroiled in legal battles to determine who owes what to whom. Odds are, Microsoft's implementation of libc is too new, and Microsoft would require a license from someone else to keep it. But the parts that are C99 were developed jointly, so it could take centuries of lawyer-time to figure out who owns what.

      We're going to hope that Google's lawyers were able to convey all of this to the Supreme Court. They'd better. There were 11 lawyers involved and the writ is 343 pages.

    4. Re: Fingers Crossed! by Anonymous Coward · · Score: 0, Troll

      Stole a Supreme Court seat from Obama, you mean.

      Mr. Obama had a year left in his term and he did his job with the nomination, but Republicans refused to do their job and even consider Garland.

      The Democrats should tell Trump "this seat is for the next president to choose." Turnabout is fair play.

    5. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      Actually, the answer is very simple -- (Song) titles can not be copyrighted. A song's title
      has no required relationship between itself and the song itself. (Say) both melodies can
      make you happy, sad, cry, etc., but can do the same thing in many different ways. Just
      like a software API - it's only the title of a function to produce an effect but can use very
      different methods to do so.

      It only makes sense that APIs are nothing more than a "title." And to think we pay the
      SCOTUS real money when all they'll wind up doing is calling me. Your Welcome!

      CAP === 'unknown'

    6. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      10 Years and no outcome!
      In woodworking, a dovetail joint, a mitre joint, or a ship with a stern and a bow. or a triangle sail. Or a cooking recipie. If this was 1970 we would see bitching over the interface of a pocket calculator layout.
        These are fundamental non copyrightable things. Years ago it was found Fujutsu did copy part of IBM's OS and VSAM and it was felt it was not clean room developed. That is solid US precedent.

      What is going to happen when AI churns out identical code for say loops or long division?
      You really want to be a Judge who rules the AI engine copied and is in violation?
      If AI generates it, or a bunch of kids in a classroom come up with the same, i should not be copyrightable. code is not artwork.

      No, you can't copyright an interface, just as you cannot copyright what holding up 2 fingers means. Well if you can, then the system has been gamed. I bet function drive and do not hit anything will be copyrighted if it could.

      I gather Google did it in a clean room implementation and was not foolish to give java source code to all the developers. I expect some pissy argument that add(1+1) is not but getJavaoperatingsystemid is.

      What a disgrace. All qualified judges do not like appealable decisions.

    7. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      Even if song titles cannot be copyrighted, if you do exact copy of all the songs of the one of the most popular albums and then you advertise that you can use listen this album in place of the other, then you are most likely violating copyright laws.

    8. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      Well there it is then, you see them as having not done their job, they probably would say that their job was to protect the court from Obama. Gridlock is a feature, not a bug.

    9. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      How does Novell own the kernel? Isn't their claim to UNIX?

      Totally unenforceable anyway. just add a character to the front of the call names - different API.

    10. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      But if that's so, then it's perfectly fair for Dems to say their job is to protect the court from Trump.

      It sets a REALLY bad precedent. Not coincidentally, it makes them look like sleazy schemind slimeballs (which they are).

    11. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      Plus both would be telling him "Is it in yet?"

    12. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      > Your Welcome!

      My welcome what?

    13. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      That's a different issue. It's the fact that two albums from different artist can have a song with the same
      title and there is no copyright problem. While we may see this as common sense, it likely was "allowed"
      because of the perceived finite number of titles (at least at the time) that were available. They didn't ever
      consider a song title like "My Bitch is M' Ho" or else those would be copyrighted as well.

      Titles are like a person's name; two people can share the same name. Same, IMHO, with a software API.
      Now the courts have screwed this up as well when a real person's name looks like a trademark. There are
      cases were Sony has won (wrongly) in these cases. The courts were too silly to understand two facts of life:
      you can't choose you mother and you can't choose your birth name.

      Argue all you want, but you'll always be wrong :) ...

      CAP === 'mullah' <=== Really /., has it come to this?

    14. Re: Fingers Crossed! by sexconker · · Score: 1, Troll

      He "did his job" by nominating someone and never fighting for their confirmation, then never challenging the "wait until after the election" bullshit.

      It was Obama's job to appoint someone. He should have kept appointing people and should have raised a big fucking stink about any delays. It's literally one of the few duties the President has.

      But no - he made a half hearted attempt and said "fuck it" for the last year of his second term. Democrats and the media didn't care because they assumed Hillary would win and they would just pick up from there.

    15. Re: Fingers Crossed! by Anonymous Coward · · Score: 1

      Ahh, but didn't Harry Reid set the stage so the party in power could steamroller the opposition? Good fun!!!!! Now that's turnabout.

    16. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      If the Scotus fucks this up, the layers will run wild for six months, but after that they have no hope of victory. People will wear yellow vests while coding.

    17. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      We're going to hope that Google's lawyers were able to convey all of this to the Supreme Court.

      Yes, I'm entirely hoping that Google can convey their point to the 9 very well-qualified jurists that have absolutely no idea about the complexity of any IP law, let alone about copyright law in particular. Good luck anticipating the ruling regardless of whether Google's point is "conveyed."

      When Justices opine about criminal prosecutions, contract law, even immigration, they've all dealt directly with some form of the questions involved and have often entertained literally hundreds of related questions in their legal careers. But patent law? Copyright? I can count on one hand the judges my circuit that have ever seen an IP case, let alone one that required them to actually understand briefs on some specific point of legal contention.

      The best we can hope for here is that they magically come up with the actual right answer in a way that doesn't fuck up something else.

    18. Re:Fingers Crossed! by Aighearach · · Score: 1

      But if Oracle wins too big, they might have to give their whole company over to K&R!

    19. Re:Fingers Crossed! by Aighearach · · Score: 1

      I like beer too, but in fairness, both sides are corporate interests.

      At least with Gorsuch, so far he's pretty consistent. Last summer he wrote a dissent wanting to get rid of the whole third-party doctrine! He might be the most willing of anybody on the bench to give copyright a constitutional smack-down!

      This could easily end up with a 6-3 decision that slashdot would love.

    20. Re: Fingers Crossed! by Aighearach · · Score: 1

      "Raising a stink" when the R's would win the vote wouldn't have achieved anything except making the R's happy.

      Your comment would be painfully ignorant if it was in good faith. But it wasn't.

    21. Re:Fingers Crossed! by junglee_iitk · · Score: 1

      While both sides are corporations, and we discussing it here are not going to do anything to anyone, it is still scary. What Oracle is claiming is that, if I built a chair, the joints of a plank are copyrightable. That is what API is - joining two different things together via a common interface. This is bullshit.

    22. Re:Fingers Crossed! by phantomfive · · Score: 1

      For those playing along at home, if the last ruling in Oracle's favor stands, Novell essentially owns the Linux kernel. The Linux kernel reimplements the UNIX kernel API. If the ruling by the blithering idiots in the Court of Appeals is allowed to stand, that's illegal without a license. Novell's lawyers would have to write a license to allow Linux to continue to exist

      This is unlikely to be true, because X/Open and POSIX were developed with the intent to be an open standard.

      For most software, it's a good idea to not use an API unless you have a license. That should be common sense by now.

      --
      "First they came for the slanderers and i said nothing."
    23. Re:Fingers Crossed! by ayesnymous · · Score: 1

      Google is asking the Supreme Court to rule, which would indicate they are very confident in their position.

    24. Re:Fingers Crossed! by AmericaRunsOnDunkin · · Score: 1

      If they fail to convince the Supreme Court to grant a hearing, it's all over and Oracle wins and software as an industry basically ends, swallowed by lawyers.... If the ruling by the blithering idiots in the Court of Appeals is allowed to stand...

      Not really. Jurisdiction is confusing even to lawyers.

      The court system is divided into circuits. There are 11 numbered circuits and DC. Each circuit covers a limited geographic area. 9th Circuit is California and the west. 2nd circuit is NY and half of New England. Etc.

      The Federal Circuit has no geographic area. They are an appeal court that handles patent and maritime cases. They almost never get a copyright case. How they got this one, I don't recall. There must have been some extraordinary circumstances.

      In any case, the Fed Circuit's rulings are only binding on the whole country where they have original jurisdiction: patents and maritime law. In other areas such as copyright, their rulings are not binding on anyone. Other circuits follow their own laws. CA federal courts follow 9th circuit rulings. NY courts follow 2nd circuit. Etc.

      At best, other circuits may look at a Fed Circuit copyright ruling as advisory. But the law in their own circuit determines the copyright rules they follow.

      This is why you often hear of Supreme Court cases as circuit splits. When e.g. the 9th circuit and the 2nd circuit make different rules, sometimes the Supreme Court steps in to unify them with one rule for the whole country. Otherwise the circuits operate independently and you get fragmented rules. This is considered a feature not a bug,

      tl;dr version - Fed Circuit rules on copyright mean jack squat. No other US court is required to follow them.

    25. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      It's pretty sad that you get enjoyment from the misery of others.

    26. Re:Fingers Crossed! by squiggleslash · · Score: 1

      Not the OP but:

      This post is about APIs, so in theory if Oracle prevails then given the Linux kernel incorporates a clean room implementation of the Unix APIs the current owner of the Unix IP would have a claim against Linux. The *BSDs might also be in the same position, depending on how the AT&T lawsuit settlement went. Scarily, C, which was also developed by Bell Labs as part of Unix, might also have the same issues.

      (Whether this is possible is another question, as the creation of the POSIX standard may itself have changed things. But I see the OP's logic and it's sound.)

      The problem here is that Oracle doesn't have much incentive to back down due to this argument. Technically they distribute "a" GNU/Linux distribution, but nothing they do is dependent upon it, and it's a tiny part of their business. Also as part of their purchase of Sun, they have full rights to the Unix APIs via SunOS/Solaris.

      --
      You are not alone. This is not normal. None of this is normal.
    27. Re:Fingers Crossed! by squiggleslash · · Score: 1

      I know you're joking but you ended up triggering my thought train on this anyway.

      As far as Unix and C goes, I think Oracle would be in the clear. They bought Sun, which gives them full rights to Solaris/SunOS. Even if that isn't enough to give them full rights to the Unix and GNU/Linux eco-system, their business is hardly dependent upon Unix technologies. Most of the stuff they sell is multiplatform.

      The more interesting one is SQL. That was created by IBM as part of System R. I suspect even if this case succeeds, and APIs like SQL turn out to be copyrightable, and IBM wanted to assert its IP at this stage, it couldn't collect much in damages because it left it too long, but it might - depending on whether it's put out language in the past claiming SQL doesn't need licensing - be able to force Oracle to stop using it. Or get a license.

      Would that kill Oracle? Alas, probably not. They'd probably just get a license. Bastards.

      --
      You are not alone. This is not normal. None of this is normal.
    28. Re:Fingers Crossed! by Shaitan · · Score: 1

      "For most software, it's a good idea to not use an API unless you have a license."

      According to whom? Clean room implemented APIs are everywhere.

    29. Re:Fingers Crossed! by Shaitan · · Score: 2

      Or they are very confident they own a lot of APIs and it wouldn't be the worst thing in the world if they had to take a hit.

      Google's recent behavior is pretty much loaded with horrible fuckery.

    30. Re: Fingers Crossed! by Anonymous Coward · · Score: 0

      Modded "Troll" when it should be "Offtopic".

      Obama should have called the Senate's refusal to hold hearings "tacit consent" and seated Garland. Either he didn't want to precipitate a "constitutional crisis" or he was so sure Hillary Clinton would be the next president anyway that he didn't bother to fight.

    31. Re:Fingers Crossed! by phantomfive · · Score: 1

      According to the courts. Having a license will avoid expensive copyright suits that you might lose. By itself, a clean-room implementation is not fair-use: the clean-room aspect merely ensures you copied no more than necessary for the purposes of interoperability. Building your implementation for the purpose of interoperability can be a fair use defense. More info is available here.

      Google tried the interoperability defense, but it failed because their software was not interoperable with Java.

      --
      "First they came for the slanderers and i said nothing."
    32. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      This is a hail Mary pass. The SC almost certainly won't rehear the case.

      The courts ruled that IBM owns the assets claimed by Novell, so it won't be Novell doing any licensing. The two cases are distinct though. It's probably not clear, and may never be clear who owns the UNIX kernel API.

    33. Re:Fingers Crossed! by Shaitan · · Score: 1

      I wasn't responding to an assertion about Google. I was responding to an assertion about "most software."

      You do not need a license to use an API or even to replicate one for interoperability as that is fair use which is essentially the only reason to do so. Your assertion with regard to "most software" requiring licensing to utilize an API is incorrect. API's don't qualify for copyright. People can sue you for most anything and buying expensive and unnecessary licenses is not automatically a better answer than the risk of expensive copyright lawsuits.

      The Google case is not yet over so google hasn't yet failed with their interoperability defense. The rational that their software is not interoperable with java is weak, the target is interoperability with java applications not java itself and Oracle has no rights to java applications (in general, obviously they have rights to specific apps). This is really no different than the WINE project. WINE would also fail to run some use cases and earlier in the project would fail in most cases, it doesn't change that the purpose of the effort is interoperability. One does not need to achieve interoperability to have interoperability as a fair use motive.

    34. Re:Fingers Crossed! by phantomfive · · Score: 1

      . API's don't qualify for copyright

      The supreme court already was asked to rule and that point, and they let the appellate court's ruling stand. APIs qualify for copyright, and there is no legal theory to distinguish APIs from any other part of code, as far as copyright goes.

      You do not need a license to use an API

      You better make sure you have one. This is mostly not a problem: most APIs you have these days already come with a license. Java did too, but Google didn't comply.

      This is really no different than the WINE project. WINE would also fail to run some use cases and earlier in the project would fail in most cases

      You clearly didn't read the link I linked to earlier.

      --
      "First they came for the slanderers and i said nothing."
    35. Re:Fingers Crossed! by Shaitan · · Score: 1

      "The supreme court already was asked to rule and that point, and they let the appellate court's ruling stand. "

      The story we are commenting under is a new request that isn't settled and most of the circuits currently agree that API's can't be copyrighted including the one that matters.

      "and there is no legal theory to distinguish APIs from any other part of code"

      APIs aren't part of the code. You really shouldn't comment on topics you are ignorant of and really neither should courts but sadly we are stuck with whatever random nonsense they spew from ignorance.

    36. Re:Fingers Crossed! by phantomfive · · Score: 1

      The story we are commenting under is a new request

      Why on earth do you think the supreme court will decide to grant the request this time?

      APIs aren't part of the code.

      Oh yeah? So this:

      "public final class String extends Object implements Serializable, Comparable, CharSequence {"

      Is not code?

      --
      "First they came for the slanderers and i said nothing."
    37. Re:Fingers Crossed! by Shaitan · · Score: 1

      I think you are confusing the API, the abstracted standard and documentation which defines the interface, with the coded definition in their implementation. It's understandable because there will certainly be a massive amount of overlap in a new clean room implementation using that abstracted standard.

      This is like a new state coming up with a drivers license and another state claiming it infringes on their copyright because it contains a picture, a dob, and a hologram and they look strikingly similar to that states and interoperability doesn't apply because the image in the hologram is different. In reality the new state took written descriptions of the security measures used by other states and came up with their own but in practice any implementation of those standards is going to end up looking similar. There are only so many ways to implement a clear head shot and so many ways to display a DOB. The same is true here but to an even greater extent, given there are common coding styles and practices a good portion of it likely would end up being identical character for character.

    38. Re:Fingers Crossed! by phantomfive · · Score: 1

      It's understandable because there will certainly be a massive amount of overlap in a new clean room implementation using that abstracted standard.

      This was not a clean-room implementation. Google was sloppy.

      I think you are confused because you don't understand the abstraction, filtration, comparison test. You can read about it.

      --
      "First they came for the slanderers and i said nothing."
    39. Re:Fingers Crossed! by Aighearach · · Score: 1

      I wasn't actually joking, I really do think that is the logical result of what Oracle is asking for, and they're asking for it because they know they won't get it. They hope to get 10 or 15 years of it only.

      Nobody they got rights from got the rights to the APIs and stuff from K&R, because nobody knew they needed it! Even just the form of a C struct; nobody thought they needed permission.

    40. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      Oh yeah? So this:

      "public final class String extends Object implements Serializable, Comparable, CharSequence {"

      Is not code?

      What does it do?

      I don't mean that in a general "what is its purpose" sense, I mean literally what instructions execute because of this line?

    41. Re:Fingers Crossed! by phantomfive · · Score: 1

      At runtime (actually when the program loads) it does boring things like allocate space in RAM where it marks the start of some function virtual method tables.

      --
      "First they came for the slanderers and i said nothing."
    42. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      That's done by boilerplate code which is pretty much the same for all functions.

    43. Re:Fingers Crossed! by phantomfive · · Score: 1

      You asked what it did. That's what it does. If you want something more specific, it also marks it with the class name, so it can be addressed through introspection.

      Regardless, even if its boilerplate, you can't deny that it's code and that it does something.

      --
      "First they came for the slanderers and i said nothing."
    44. Re:Fingers Crossed! by squiggleslash · · Score: 1

      The rights to K&R are part of the wider Unix IP package, and they definitely, via Sun, have full rights to that. C was developed as part of Unix, and K&R (at least, the first edition) was literally just a description of C under Unix.

      --
      You are not alone. This is not normal. None of this is normal.
    45. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      > You asked what it did. That's what it does

      No, it doesn't. It defines an interface that is then passed into boilerplate code.

      > Regardless, even if its boilerplate, you can't deny that it's code and that it does something.

      What I'm saying is that it is essentially generic code. It gets translated into boilerplate function setup code that would be pretty much the same for any number of interfaces, and you can't make a working program without it. Apart from the naming, there is no creative element to it.

    46. Re:Fingers Crossed! by phantomfive · · Score: 1

      Apart from the naming, there is no creative element to it.

      Apart from the naming, organization, and deciding what the functions will actually do.

      --
      "First they came for the slanderers and i said nothing."
    47. Re:Fingers Crossed! by Anonymous Coward · · Score: 0

      For the line you provided, you've got to choose names and then order the parameters.

      What the function actually does is irrelevant to the interface description. It's a black box.

    48. Re:Fingers Crossed! by phantomfive · · Score: 1

      For the line you provided, you've got to choose names and then order the parameters.

      I also chose what it inherited from, which gets embedded in the compiled product.

      --
      "First they came for the slanderers and i said nothing."
    49. Re:Fingers Crossed! by tricorn · · Score: 1

      The fair use defense is for doing reverse engineering (which involves copying protected expression) for the purpose of discovering the "functional requirements for compatibility", which are not protected by copyright. 102(b), Sega

      If you can find out the information another way, such as if the specifications are published and freely available, there's no need to do reverse engineering, and any copying of protected expression for reverse engineering purposes would not be fair use any longer.

      What you do with that information is not restricted to creating compatible software, nor is it even about fair use at that point. That information is simply not protected by copyright.

    50. Re:Fingers Crossed! by tricorn · · Score: 1

      Google was a bit sloppy, Harmony less so. Ultimately, it didn't matter, the one method that was inadvertently copied (rangeChevk) was the ONLY code that was found to infringe, other than the declarations, and the damages were found to be $0.

      Properly done, AFC would filter out the declarations from consideration, assuming Google is correct and the (abstract) Java API is not protected by copyright.

    51. Re:Fingers Crossed! by tricorn · · Score: 1

      Why on earth do you think the supreme court will decide to grant the request this time?

      a) the question is much better;
      b) the case has ripened considerably;
      c) the CAFC didn't fix their mistakes.

      So this:

        "public final class String extends Object implements Serializable, Comparable, CharSequence {"

      Is not code?

      Sure, that's code. It describes a portion of an API, a class definition.

      While the code can be copyrighted, Google's question asks if the API itself is copyrighted, or is it a functional "system or method of operation" and excluded from copyright protection by 102(b) (including the names).

      If it is excluded by 102(b), then the code you wrote would also not be protected, because of merger (the 97% of the code that isn't declarations would still be protected).

      It's not that "declarations" have some special powers, but that declarations in Java are, by design, required to be almost identical when describing the same API.

    52. Re:Fingers Crossed! by phantomfive · · Score: 1

      a) the question is much better;

      It's not, I've read their petition, and it's crap. The appellate court came up with a logical, consistent way to apply copyright law, and the Google petition is not.

      It's not that "declarations" have some special powers

      Yes, that's exactly right.

      --
      "First they came for the slanderers and i said nothing."
  2. IP Law - Home to Roost by chuckugly · · Score: 2, Insightful

    It's somehow pleasing to see a huge copyright holder get shafted by the laws they helped promote. Hey Google, if this stuff went into the public domain in a timely manner like it's supposed to you wouldn't have your tit in a wringer right now.

    1. Re:IP Law - Home to Roost by Anonymous Coward · · Score: 0

      It's somehow pleasing to see a huge copyright holder get shafted by the laws they helped promote.

      Current copyright law was enacted in 1976, does Google have a copyright on time machines?

    2. Re:IP Law - Home to Roost by Narcocide · · Score: 1

      You had better check before you place any bets.

    3. Re:IP Law - Home to Roost by EvilSS · · Score: 2

      Pretty sure the BBC holds the copyright on those.

      --
      I browse on +1 so AC's need not respond, I won't see it.
    4. Re:IP Law - Home to Roost by Aristos+Mazer · · Score: 5, Informative

      Google was barely around for the Mickey Mouse copyright extension of 1998*. That was all Disney, not Google. Google has pushed for lots of widening of fair use law (like the ability to quote web pages as part of search results), but hasn't gotten a whole lot of budge.

      * Google was founded in Sept 1998. I'm not sure exactly what month the extension passed Congress, but I guarantee Google didn't have a seat at the table back then.

    5. Re: IP Law - Home to Roost by houghi · · Score: 1

      They want to know when to copyright, not when it is free to use.

      --
      Don't fight for your country, if your country does not fight for you.
  3. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    Google has no right to Oracle IP.
    Just because they bought an implementation of a knockoff of Java so obvious everyone thinks it IS Java does not give them rights. Why would the Supreme Court listen to yet another ridiculous claim on Java? Huh? Why?

  4. Re:Use Java? Then you deserve whatever happens. by Narcocide · · Score: 5, Funny

    You fucking take that shit about BASIC back right this second.

  5. Eric Schmidt is a Piece of Shit by Anonymous Coward · · Score: 0

    Not commenting on this specifically, just in General.

  6. The U.S. legal system is often disfunctional. by Futurepower(R) · · Score: 1

    The U.S. legal system needs many, many improvements.

  7. It's copyrighting the electric socket by lamer01 · · Score: 1

    It's an interface. It should not be allowed to be copyrighted.

    1. Re:It's copyrighting the electric socket by aberglas · · Score: 1

      IBM have been patenting interfaces for decades.

      It is not the job of the court to decide whether the law makes sense. Merely how it applies.

    2. Re:It's copyrighting the electric socket by rahvin112 · · Score: 1

      Yea, well the only way the SC will take it up is if they get flooded with friend of the court briefs by companies that will be affected by the ruling. Any company relying on an API created by someone else should be immediately filing those. If the appeal is allowed to stand there's going to be a LOT of lawsuits.

    3. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Individual api signature may not be copyrighted but collection of large set of api can be copyrighted. With yellowbook, there was a ruling that direct copy of yellowbook was a violation but you can recompile your own data and publish. Google did direct copy. They didn't provide equivalent api, they provided the exact api.

    4. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Good. It's high time companies stop using APIs provided by others to suck data and spy on us and exchange data about us. APIs should be forbidden.

    5. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Patenting, not copyrighting. Big difference.

    6. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      I agree in principle, but Devil's advocate here.

      Think back to when Microsoft came out with J++ in an attempt to destroy this threat to the Windows monopoly call Java (people bought Windows, no matter how horrible, because that is what all the software ran on). It was Java with just a few extensions - enough to suddenly make it no longer platform independent. Since most people were using Windows for software development, most Java applications and code would suddenly become platform/OS dependent.

      Sun sued, won, and we are better for it. Java was neither fractured nor destroyed.

      Now, Oracle is the bad guy when Google is doing the exact same thing Microsoft tried in the late 90's. The motivation may be different (they are not trying to destroy Java), but the effect is the same on the language. They have developed their own version of Java that is not compatible with Java. That is bullshit. I don't want it to be allowed.

    7. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Now, Oracle is the bad guy when Google is doing the exact same thing Microsoft tried in the late 90's. The motivation may be different (they are not trying to destroy Java), but the effect is the same on the language. They have developed their own version of Java that is not compatible with Java. That is bullshit. I don't want it to be allowed.

      You'd better un-GPL Java then. Sun opened it in 2006.

    8. Re:It's copyrighting the electric socket by tricorn · · Score: 1

      No, they only provided a portion of the Java API, then added much more of their own (and created independently the other 97% of the source code of the portions of the API they did copy, the actual implementation).

      The claim is that the API as a whole is a "system or method of operation", so those parts necessary to describe that API (the declarations) are not protected (because 102(b) says that "systems" and "methods of operation" are excluded from protection).

      Thousands of names are not needed to make something copyrightable. The threshold is quite low. The one part of the Java API source code that Google actually (unintentionally) copied was only nine almost trivial lines, yet that was long enough to be found infringing. The difference was that those weren't declarations, they were the body of a method (a "function" or "procedure" or "subroutine" in other languages), so there were many ways it could have been written and have the exact same function, so the description of the function is copyrightable, even though the function itself isn't.

    9. Re:It's copyrighting the electric socket by tricorn · · Score: 1

      Microsoft lost because they tried to call it "Java", without having a license to use the trademark.

      Google never called it Java, never claimed it was Java, only tried to make the core of the API compatible.

    10. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      > Google never called it Java, never claimed it was Java, only tried to make the core of the API compatible.

      Oh really ?

    11. Re:It's copyrighting the electric socket by tricorn · · Score: 1

      Yes, really. They use the " Java programming language", which Oracle agrees that anyone can use.

      They neve claim they are using the Java API.

      "Android includes a set of core libraries that provides most of the functionality available in the core libraries of the Java programming language."

    12. Re:It's copyrighting the electric socket by tricorn · · Score: 2

      The lawsuit with Microsoft was about trademark and breach of contract. Sun failed in a copyright action against MS.

      The case against Google is copyright, not trademark. Google never claimed that their platform was Java, as in the Java Platform, using the Java trademarks.

      The linked page says Google uses the Java programming language (which they do) and implements parts of the Java API (which they do). None of that is claiming to be Java, nor do they use any Java trademarks.

    13. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Copyright has been claimed in the standard interfaces before in the Unix world, and then given permission to implement freely - ignoring claims for any patents - for the benefit of the ecosystem as the youngsters say it these days. Oracle has the previous claims to fall onto, Google has the public benefit on their side. How does the Public benefit vs. Previous legal claims weighting goes in the US case law?

    14. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      GPL is revocable by the grantor, being a bare license with no attached interest...

      >p46 "As long as the project continues to honor the terms of the licenses under which it recieved contributions, the licenses continue in effect. There is one important caveat: Even a perpetual license can be revoked. See the discussion of bare licenses and contracts in Chapter 4"
      --Lawrence Rosen

      >p56 "A third problem with bare licenses is that they may be revocable by the licensor. Specifically, /a license not coupled with an interest may be revoked./ The term /interest/ in this context usually means the payment of some royalty or license fee, but there are other more complicated ways to satisfy the interest requirement. For example, a licensee can demonstrate that he or she has paid some consideration-a contract law term not found in copyright or patent law-in order to avoid revocation. Or a licensee may claim that he or she relied on the software licensed under an open source license and now is dependent upon that software, but this contract law concept, called promissory estoppel, is both difficult to prove and unreliable in court tests. (The concepts of /consideration/ and /promissory estoppel/ are explained more fully in the next section.) Unless the courts allow us to apply these contract law principles to a license, we are faced with a bare license that is revocable.
      --Lawrence Rosen

      >p278 "Notice that in a copyright dispute over a bare license, the plaintiff will almost certainly be the copyright owner. If a licensee were foolish enough to sue to enforce the terms and conditions of the license, the licensor can simply revoke the bare license, thus ending the dispute. Remeber that a bare license in the absence of an interest is revocable."
      --Lawrence Rosen

      Lawrence Rosen - Open Source Licensing - Sofware Freedom and Intellectual property Law

      >p65 "Of all the licenses descibed in this book, only the GPL makes the explicity point that it wants nothing of /acceptance/ of /consideration/:
      >...
      >The GPL authors intend that it not be treated as a contract. I will say much more about this license and these two provisions in Chapter 6. For now, I simply point out that the GPL licensors are in essentially the same situation as other open source licensors who cannot prove offer, acceptance, or consideration. There is no contract."
      --Lawrence Rosen

      ----
      >David McGowan, Professor of Law, University of Minnesota Law School:

      >"Termination of rights

      >[...] The most plausible assumption is that a developer who releases code under the GPL may terminate GPL rights, probably at will.

      >[...] My point is not that termination is a great risk, it is that it is not recognized as a risk even though it is probably relevant to commercial end-users, accustomed to having contractual rights they can enforce themselves.

    15. Re:It's copyrighting the electric socket by squiggleslash · · Score: 1

      Periodic reminder that patents, copyrights, and trademarks are different things.

      Patents: "I came up with this technology myself. I'm going to stop you from using it for 20 years without my permission by registering it with the patent office, who might refuse to grant a patent. It doesn't matter if you invent the same thing independently without knowing how I did it, you can't do it for 20 years." (There's also stuff called "Design patents")

      Copyrights: "This creative work may not be copied, without my permission, until 70 years after my death. If you somehow manage to create the same thing yourself, don't worry, it's only if you copy my ideas that you're in trouble." (There are also special rules for recordings of specific performances, and each element of a performance of someone else's work. Also corporately owned copyrights have a different time limit, as do older works.)

      Trademarks: "You can't call yourself 'Disney Trademark Lawyers' without our permission. This will be the case until we decide to stop using the trademark, or our company ceases to exist and nobody buys the trademark, or if people keep using it to describe something generic related to our business. You may use it in cases where there's no confusion, for example you can write "Oracle sucks" or start an IBM Grocery chain. My application for a trademark may sometimes be rejected but it's rare."

      --
      You are not alone. This is not normal. None of this is normal.
    16. Re:It's copyrighting the electric socket by Shaitan · · Score: 1

      "Sun sued, won, and we are better for it. Java was neither fractured nor destroyed."

      In what way are we better for that? Java is only used so widely because schools pumped it out to legions of students.

    17. Re:It's copyrighting the electric socket by Anonymous Coward · · Score: 0

      Sure, but in none of those cases does "being an interface" play a part.

    18. Re:It's copyrighting the electric socket by nctritech · · Score: 1

      Last I checked, most of what we use today is either a direct copy of or influenced by UNIX from Bell Labs. If APIs are copyrightable and copyrights last at least 70 years, it seems to me that almost every modern OS and program is likely to be violating the copyrights of whoever owns that chunk of Bell Labs now...including Oracle. APIs must not be allowed to fall under copyright law; it's the computer equivalent of copyrighting a bunch of basic words and phrases, or 70+-year-patenting the classic box-end wrench. Can you imagine the clusterfuck if EVERYONE had to re-invent not just the wheel, but the whole car, by law?

  8. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    But that is the question here... Oracle owns copyright to Java but it published an interface for making compatible software and now it's crying because Google has something that complies with the interface but doesn't pay money to Oracle. So are the Java APIs also protected by copyright? They are essentially a technical description, like a table or a measurement, which in other domains isn't protected.

    This is fundamental to how people will interact with open source or proprietary software.

    If Oracle wins, there will be a new movement to get a free programming language and free toolchain for it that people can use... And leave Oracle in the dirt. Kotlin will need to go all native and ditch it's Java roots.

    No, Ruby and Smalltalk are not suitable substitutes. No, Python and BASIC and Fortran aren't either.

  9. ITS BLOODY SIMPLE by Anonymous Coward · · Score: 0

    I was always taught that the x.C / x.C++ file was copyright and held the IP and must not be copied but the x.h / x.hpp etc was just interface or
    instructions on how to talk to the implementation in the x.c / x.cpp file.

    Any other way of handling this is just basic fucking stupidity...
    fairly average c cpp asm programmer

    AND i HATE PROVING IM HUMAN!

  10. Progressive? by Anonymous Coward · · Score: 1

    You progressives are remarkably bigoted.

  11. GPL can be revoked. by Anonymous Coward · · Score: 0

    >p46 "As long as the project continues to honor the terms of the licenses under which it recieved contributions, the licenses continue in effect. There is one important caveat: Even a perpetual license can be revoked. See the discussion of bare licenses and contracts in Chapter 4"
    --Lawrence Rosen

    >p56 "A third problem with bare licenses is that they may be revocable by the licensor. Specifically, /a license not coupled with an interest may be revoked./ The term /interest/ in this context usually means the payment of some royalty or license fee, but there are other more complicated ways to satisfy the interest requirement. For example, a licensee can demonstrate that he or she has paid some consideration-a contract law term not found in copyright or patent law-in order to avoid revocation. Or a licensee may claim that he or she relied on the software licensed under an open source license and now is dependent upon that software, but this contract law concept, called promissory estoppel, is both difficult to prove and unreliable in court tests. (The concepts of /consideration/ and /promissory estoppel/ are explained more fully in the next section.) Unless the courts allow us to apply these contract law principles to a license, we are faced with a bare license that is revocable.
    --Lawrence Rosen

    >p278 "Notice that in a copyright dispute over a bare license, the plaintiff will almost certainly be the copyright owner. If a licensee were foolish enough to sue to enforce the terms and conditions of the license, the licensor can simply revoke the bare license, thus ending the dispute. Remeber that a bare license in the absence of an interest is revocable."
    --Lawrence Rosen

    Lawrence Rosen - Open Source Licensing - Sofware Freedom and Intellectual property Law

    >p65 "Of all the licenses descibed in this book, only the GPL makes the explicity point that it wants nothing of /acceptance/ of /consideration/:
    >...
    >The GPL authors intend that it not be treated as a contract. I will say much more about this license and these two provisions in Chapter 6. For now, I simply point out that the GPL licensors are in essentially the same situation as other open source licensors who cannot prove offer, acceptance, or consideration. There is no contract."
    --Lawrence Rosen

    ----
    >David McGowan, Professor of Law, University of Minnesota Law School:

    >"Termination of rights

    >[...] The most plausible assumption is that a developer who releases code under the GPL may terminate GPL rights, probably at will.

    >[...] My point is not that termination is a great risk, it is that it is not recognized as a risk even though it is probably relevant to commercial end-users, accustomed to having contractual rights they can enforce themselves.

  12. "The company says new issues are now at play," by Anonymous Coward · · Score: 0

    Which I guess means that sufficient bribes have been placed to change some minds. Nice that Google has so much money that they can apply this approach each time they lose. However, one can only ask -- Where's mine?

  13. Re:Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    MySQL was bought by Oracle. Why would a "serious" database company tarnish their name with that?

  14. API==program is like water==plumbing by OldMugwump · · Score: 1

    I think the confusion here is because it's called an "application PROGRAMMING interface". Despite having the word "programming" in it, an API is not a program.

    APIs are to programming as plumbing is to water. Or as electricity is to an electric socket. NOT the same thing at all.

    It's as if we said "you can copyright electricity", and then somebody said well it's called an "electrical connector", therefore I can copyright it.

    --
    "Shoot, a fella could have a pretty good weekend in Vegas with all that stuff."
  15. Who owns the Posix/*nix API by aberglas · · Score: 3, Interesting

    If Google loses, what happens to Unix?

    I can imagine that the court would rule that merely copying the style of the API is not copyright. But copying the exact text of it, down to the names of the methods is another matter entirely.

    You cannot copyright a genre of novels, or the types of characters within. But you can certainly copyright specific characters with specific names.

    It flows exactly to *Nix. SCO might live again.

    We would have to go through all of our applications and rename the methods. Or new legislation would need to be passed, which is unthinkable.

    Interestingly, a big loser in that would be Oracle themselves. They should have bought SCO (or whoever now "owns" Unix) before starting this. Then they could have it all.

    1. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      Sun paid full and final license fee to SCO to perpetually use source code of Unix. So they won't get affected. IBM maybe, Redhat maybe.

    2. Re:Who owns the Posix/*nix API by davecb · · Score: 1

      To Novell, actually, who had used SCO as an agent. Sun didn't exactly like SCuM.

      --
      davecb@spamcop.net
    3. Re:Who owns the Posix/*nix API by Aighearach · · Score: 1

      Then they'll have to start digging into the question: Since writing a client that uses a whole API is clearly a copyright violation, what percent of an API can you use within the confines of "fair use?"

      If google loses, a whole shitstorm of fights about the boundaries of fair use will be mandated.

      Anything that uses a whole API will obviously be out. The future will be giant bloated APIs so that people can fairly use a large enough portion to end up with a useful program. Or mixing a few calls each to a bunch of different libraries that do the same thing differently.

      Oracle might not be that big a loser; their database has worst-of-class integration, and java isn't worth that much.

    4. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      I would maintain that an API is not a copyrightable work in itself; it is a list of facts about a copyrightable creative work.

      I have an unofficial book about Star Trek that describes all the characters. I doubt that the authors licensed the characters from Paramount, but I suppose it's possible.

    5. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      I think another interesting question here is "where the fuck does Oracle actually think they are headed with this?". After all, it's not like they invented SQL, for instance. They are literally sawing off the branch they are sitting on there, and in may, many other ways.

      It's a brilliant example of why greed isn't good, it blinds you to the consequences of actually getting what you want.

    6. Re:Who owns the Posix/*nix API by Krishnoid · · Score: 1

      Everyone will finally have to move to GNU, I guess.

    7. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      The Harry Potter author successfully sued someone for a website along those lines.

      Nothing is clear.

    8. Re:Who owns the Posix/*nix API by phantomfive · · Score: 1

      If Google loses, what happens to Unix?

      POSIX is fair use. Although the API may be copyrighted, POSIX was created to enable interoperability, by the copyright holders themselves. These things favor fair use.

      --
      "First they came for the slanderers and i said nothing."
    9. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      If you're referring to this case, it appears that as a general rule, such references are indeed legal:

      https://en.wikipedia.org/wiki/The_Harry_Potter_Lexicon

    10. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      If it isnt copyrightable, then licenses are not a thing anymore and everything gpl will go closed source in an instant.

    11. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0

      Not only fair use (for the purposes of interoperability), but use with the explicit permission of the copyright holders (minus any patents). In that way it doesn't solve the issue for Google's benefit by default. Fair use would be the use of a copyrighted work without such explicit permission in the extent that is allowed in the copyright law, as I see it. I don't know if there is such an interoperability exception in the US copyright law, but if there is it should apply.

    12. Re:Who owns the Posix/*nix API by phantomfive · · Score: 1

      but use with the explicit permission of the copyright holders (minus any patents).

      I think that is true, but I haven't been able to find the license or permission anywhere.

      I don't know if there is such an interoperability exception in the US copyright law, but if there is it should apply.

      It's not explicitly written in the law, but some court cases have found it a valid defense.

      --
      "First they came for the slanderers and i said nothing."
    13. Re:Who owns the Posix/*nix API by Anonymous Coward · · Score: 0
  16. Re:With Google's Chromeium ... by Anonymous Coward · · Score: 0

    Once you get license for Chromium, you get license to program it. What google can do is prevent another browser implement the Chromium api if they own them. For example, if Chromium provides api like "readAllProvideDataAndScrewUser()". It can prevent others to implement exact same api signature.

  17. Re:Fingers Crossed! -- Hope Oracle stays win . by Anonymous Coward · · Score: 0

    Good. Women already took over linux in the USA.

    It will just have to move back to it's roots: an "I don't give a shit about the law" hacker OS.

    I hope Oracle keeps it's win.

    Oh and the GPL is revocable at will and always has been, the whole thing could have collapsed at any second.

    It is not the USA legalities that made linux or OSS.
    It is the men.

    NOT the law abiding cunts.
    Here's looking forwards to the destruction of the US software industry.

  18. Re:Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 1

    Wow, I can tell you really know your stuff. No one in their right mind would use Java. Any day now everybody will see the error of their ways and stop using it.
    You so smart!

  19. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    It licenses the interface to develop compatible software and Google refused to license.

  20. GPL and copyright licenses by Anonymous Coward · · Score: 1

    Al: the FSF was so insistent on the adoption of the GPL version 3
    because the GPL version 2 is not operative against the grantor.

    This deficiancy was, in their eyes, so fatal to the purposes that they
    invisioned that they, as you have pointed out, ellected to employ
    enhanced means of converting projects to version 3.

    Eben Moglen's contention that the GPL 3 exists to internationalize the
    GPL is a lie of omission.

    It is true that that is a partial reason-to-be for the GPL version 3
    but it is not the main nor most important reason for the insistence on
    version 3 or "v2 or any later version".

    The very heart of the GPLv3 is the addition of the "irrevocable by
    grantor" clause and the "term of years" clause.

    Additionally the contention by the FSF and, as I recall, Eben Moglen
    that the reason the FSF only accepts code where the copyright is
    transfered to the FSF - is so they may have standing to sue - is
    another lie by omission.

    Yes, standing to sue is vital, if you are going to sue.
    But the real beating heart of the copyright assignment policy is to
    prevent a programmer from rescinding license-to-use regarding his
    freely given code.

    Without copyright assignment, any contributor to the GNU project could
    elect to rescind the gratis license grant at his pleasure, at any
    time, as of right.

    Without an "irrevocable by grantor" clause (as seen in the GPL version
    3, but ommitted in GPL version 2 due to a mis-assumption on the part
    of the drafter) there is not even an affirmitive defense of promissory
    estopple.

    We come to lie number three. (Neccecitated by:)
    The incorrect assumption made by the
    drafter of version 2 of the GPL and memorandized by Eben Moglen in
    this very thread in an attempt to protect the error in drafting.
    Lie number three: If terms regarding termination are proffered in a
    copyright license they are the only means of termination.

    This is true... If those terms are supported by bargained-for
    consideration.
    That is: the words Eben Moglen wrote were true; as regards to
    commercial software, where the licensee has paied valuable
    consideration for the terms offered.

    The drafter of version 2 of the GPL was familiar with such commercial
    licensing agreements. He failed in his due-dilligence if RMS did
    indeed request an irrevocable-by-grantor license. The drafter stopped
    his research at the typical copyright license stage, and did not
    research furthur into what underlys the constuction there-of.

    And thus we have the lie of ommission number 3.

    (All, naturally, to protect Eben Moglen's former client and to
    discourage litigation where there is, indeed, good and sufficent
    cause for such litigation) (Which is all part of an attorney's
    duties, I can assure you)

    1. Re:GPL and copyright licenses by Aighearach · · Score: 1

      I am not a lawyer and this is not legal advice.

      None of what you said means that you can enforce a claim where you granted a license, though. Revoking the license does not revoke the contract that created the license.

      If you grant a permanent license, that grant is a contract. If you revoke the license without a new agreement, you've placed yourself in violation of the original contract; you'll be required to return the license in the end. And you may be formally found to have been naughty, even.

      The stuff about being irrevocable is for a related purpose. When they use copyright assignment as a means to be in control, rather than licensing, their only contract is revocable by statute! They can't go back in time and get a permanent license before getting the assignment, and once the assignment happens they can't get a separate use license directly. So they make the license that they give out irrevocable, so if their own license ever got revoked both they and their users would be protected.

      The situation doesn't even apply when the authors keep their copyright and everybody just agrees on a license. Then there is nothing that was ever revocable! It is just a special situation where the software is published under assigned copyright, and without a contract separate from the assignment contract.

      My advice, keep your copyright, publish under Apache 2 license, everybody can copy, GPL, BSD, proprietary, doesn't matter. If you don't want it get copied, don't release it. If you do want it to get copied, don't restrict it.

    2. Re:GPL and copyright licenses by Anonymous Coward · · Score: 0

      The GPL is not a contract. That is the point. That is why it is revocable.

      It is a bare license. YOU have given no consideration for the "terms" to bind the grantor.

      Indeed, you are not a lawyer, and your "advice" is not legal advice. It is mublings of yet another "know everything" techie.

      A license, absent an interest (usually $$) is revocable.

  21. It's a good thing APIs weren't copyrightable in the olden days or Compaq would have been shut down on their firmware clone and there's be no PC industry and IBM would still be the bad guy and Apple would have died after their 1984 commercial and you'd be stuck with CGA video and 640k of RAM.

    --
    (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
    1. Re:Whew by Anonymous Coward · · Score: 0

      IBM/Compaq was more about "reverse engineering" than "copyrightability."

    2. Re:Whew by Aighearach · · Score: 1

      We wouldn't even be able to use the CPU features in ASM without a new license from the vendor.

      The whole world would have to switch to RISC-V! /s

      ARM already has CMSIS though. So not really.

    3. Re:Whew by Aighearach · · Score: 1

      Oracle wants to ban forwards engineering too! That's the main difference.

    4. Re:Whew by phantomfive · · Score: 1

      Copying for the purpose of interoperability is fair use. There is legal precedent on this point, Sega vs Accolade.

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

      The issue of reverse engineering and whether it is allowed is purely a copyright issue, that's the only thing that could prevent it.

    6. Re:Whew by AmiMoJo · · Score: 1

      Probably not though. Like Betamax the IBM PC would have eventually failed and be replaced by something more open, and thus cheaper and better supported. VHS wasn't even as good in terms of picture quality.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  22. JHMFC. Overreact much? by Anonymous Coward · · Score: 0

    ... For those playing along at home, if the last ruling in Oracle's favor stands, Novell essentially owns the Linux kernel. ...

    JHMFC, Are you always prone to such overreactions?

    Freely-available UNIX implementations have been available for DECADES . BSD. Linux. Hell, Solaris was open-sourced at one point.

    And the owners of what you call "the UNIX kernel API" did NOTHING.

    Read: https://en.wikipedia.org/wiki/Estoppel#United_States

  23. Re:Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    The butthurt is strong in this one.

  24. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    Not exactly. Sun bought MySQL before the Oracle acquisition. The last CEO of Sun did a lot of nonsensical things in a desperate effort to save the company after its market changed.

  25. Re:JHMFC. Overreact much? by Areyoukiddingme · · Score: 5, Interesting

    Freely-available UNIX implementations have been available for DECADES . BSD. Linux. Hell, Solaris was open-sourced at one point.

    And the owners of what you call "the UNIX kernel API" did NOTHING.

    Doesn't matter. Estoppel doesn't apply. Novell didn't make any promises not to exert their copyright. They didn't know they could exert their copyright, until the Federal Circuit starting blathering around in not one but two idiot rulings. Depending on who you ask, they still can't. The Second, Fifth, and Tenth Circuits all say APIs aren't copyrightable at all, so the whole question of fair use is moot. The Third and Federal Circuits say they are copyrightable. The Federal Circuit went even farther, saying they're copyrightable and there's no way to make fair use of any API.

    I read the 21 relevant pages from Google's writ, and I'd say it'll be granted. The second half of it hinges on fair use, and it's a weaker argument. The first half is all about the disagreements among the circuit courts, and that always attracts the attention of the Supreme Court.

    Google's lawyers did attempt to address the earth-shattering ramifications if the Federal Circuit's ruling is allowed to stand, but not as much as I'd like. Hopefully they were saving the best parts of that for oral arguments. This Supreme Court has spent years asking, "Where's the harm?" and if you can't answer, you lose. If Google's lawyers successfully convey the harm, they have a good chance. They'd better describe the harm to all software everywhere though, not just the harm to Google software.

    Google did point out that the Federal Circuit (full name United States Court of Appeals for the Federal Circuit) is disingenuous at best, malicious at worst, in their second overturning of the jury verdict that declared Google's use of Java APIs fair use. The Federal Circuit said that they assumed all findings of fact were completed by the jury (as they're required to do), then they contradicted both themselves and the jury and tossed out the verdict. I'm starting to wonder if the Federal Circuit botched their ruling on purpose in order to precipitate intervention by the Supreme Court.

  26. Re: Use Java? Then you deserve whatever happens. by Areyoukiddingme · · Score: 1

    It licenses the interface to develop compatible software and Google refused to license.

    Licensing something to me that you don't own because you can't own it is fraud, not some ex post facto justification that a thing can be owned.

    SCO spent years trying that shit, and ultimately lost, on every front. Their very last attempt was shut down in 2016, dismissed with prejudice, which means they're not allowed to ever make the argument again.

  27. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    SCO case was about copying implementation and not interface. Since the implementation was clean and not copied, it lost the case. This has nothing to do with this case. In this case, Google accepts that it did what Oracle says it did. The question is whether it is allowed or not. In SCO's case, IBM never agreed to SCO's claim that it copied the said code.

  28. Song titles aren't thousands of words long by raymorris · · Score: 1

    I'm not saying you're wrong in your conclusion that the Java API can't be copyright, but I'm not convinced by your argument.

    Titles of popular songs:
    Come Home
    Stay
    One
    Smile
    I Love You

    Given that song titles are typically 1-3 words, of course the same word is used as a title for multiple songs. In many cases there are ten different songs to hit the billboard charts with the same title.

    The Java API is thousands of words. (Grotesquely oversized, some would say). The only way you end up with the same thing that Java made is if you intentionally copy them. In fact, you'd have to copy them very carefully, it would be easy to mess up and have a method take arguments in a different order or something.

    With song titles, if you pick any common English word, that's probably the title of an existing song. You almost can't avoid using the the same title. With Java, it's very hard to copy it exactly. It's also very easy to write an API that's just as good, or in fact better, that isn't identical to Java.

    Song titles aren't copyrighted because they are one or two words, maybe three. Other people have already used the same title before and they will again purely by chance. The same is not true of Java.

    1. Re:Song titles aren't thousands of words long by Aighearach · · Score: 1

      You don't understand their claims. At all.

      They're not only claiming copyright on the work as a whole, they're claiming that each API call is a copyrighted passage, just like each sentence in a book is copyrighted. They're saying that the name of a method or function, along with its arguments, is a copyrightable creative passage.

      There is literally only one word that is non-functional in that. So yes, it is exactly the same as copyrighting the name of a song.

      We're talking purely about the interface definition. We're not talking about writing a new API, we're talking about being allowed to write a new API with the same interface, and in this case, simply to use the API. Use of the API is a copyright violation according to Oracle, because you're using the same method names and arguments.

    2. Re:Song titles aren't thousands of words long by rtb61 · · Score: 1

      It extends further out into similar algorithms in terms of function written in different languages. Once it is written in one language it is often an auto translation into another, can you keep copyrighting the same instructions from language to language. Can I simply grab your code, translate it into a new language and claim new algorithm, because they will be different. So it is expressions of function, not creative writing, those expressions of function are bound to the coding language and the problem to be solved, based upon the language, there will always only be one best way to solve any problem, in terms of compact, accuracy and code function. Writing software has much more in common with writing maths equations that writing a book, it is far more tilted to set expressions to solve set problems. You can not programme it in an alternate fashion, the code language binds you to a set best method for any specific problem.

      It is akin to claiming copyright on lego block house, of set size and form and claiming yours is unique, when only one most efficient solution is possible. It is less creative writing and more assembling bits of code language.

      --
      Chaos - everything, everywhere, everywhen
    3. Re:Song titles aren't thousands of words long by tricorn · · Score: 2

      There are several aspects to this. What you seem to be talking about is "substantial similarity", to show that copying occurred, because it's unlikely that it would happen just by chance.

      To be infringing, there must be copying, since independent creation is allowed. However, some aspects of a copyrighted work are not protected by copyright, and even if you do copy those parts, there is no infringement.

      102(b), that Google references, says that various specific abstractions can't be copyrighted (as opposed to something like a plot or a story). If an "idea" is too abstract, it can't be owned. Processes and procedures, concepts, discoveries, systems , and methods of operation are also excluded from protection.

      If you copy a story, even if you use completely different words, even if you tell it in a different style, you can still be infringing on the story (if the story was original AND you copied it rather than come up with it independently). That's because "story" isn't excluded by 102(b). In particular, it isn't so abstract("idea") that it is no longer "expression" (and maybe has become "concept").

      An algorithm is excluded ("process" or "procedure"). Facts are excluded ("discovery"). Recipes are excluded ("procedure", and a list of ingredients isn't considered to be creative). The descriptions of all of these can be copyrighted, but that can't block someone from using your work to create new descriptions of the same thing.

      Google's claim is that the abstract Java API is a "system or method of operation", and that it includes the specific names as part of that. That means you can write a book (in your own words) describing the Java API, and you can include the actual names used in that API when describing it.

      If you can't describe something that is excluded by 102(a) without using specific language, even that literal language isn't protected by copyright (this principle is called "merger"). In the Java language, there is only one way to declare a function (a "method signature"), a class, a constant, so if those elements (including the names) are excluded by 102(b), then the declarations are, by merger, unprotected by copyright.

      The only parts of the Android API and Java API source code that are the same are those parts of the declarations that can't be changed without changing the API. If you were to start off with that book describing the Java API, even if it has no source code in it, you'd end up with the exact same declarations even if you had no access to the Java API source code and thus had no way to copy it. The only thing you'd be copying is the abstract Java API itself (including the names). If that is excluded from copyright protection by 102(b), then there is no infringement.

      That's one of the questions Google asks of the Supreme Court, if the Java API is excluded from copyright protection by 102(b).

      Note that a list of names, if it can be protected by copyright at all, has a very weak copyright. Unless you copy the exact same list, with only "trivial" changes, there is no infringement Google copied only a portion of the Java API, and added a lot more of its own. The differences between them is significantly more than "trivial".

    4. Re:Song titles aren't thousands of words long by phantomfive · · Score: 1

      They're not only claiming copyright on the work as a whole, they're claiming that each API call is a copyrighted passage, just like each sentence in a book is copyrighted. They're saying that the name of a method or function, along with its arguments, is a copyrightable creative passage.

      It's more than that. It was the structure, sequence, and organization of the APIs. So Math.max() is probably not copyrightable, but Java.lang.math.max(), when combined with thousands other functions in the same library, is also copyrightable. Google didn't need to use the Java prefix.

      The Java creators needed to make decisions like, "should Exception go into Java.lang, or should it go into java.runtime? Should String go into java.object, or should it go into java.util? Where should vector go?" So the organization of these things is creative (and even Google admits that).

      Ultimately, if the supreme court declines to overturn this case, then it means you should not use an API without a license. Build your own.

      --
      "First they came for the slanderers and i said nothing."
  29. Fingers Crossed? No, choose a better case by davecb · · Score: 1

    Google needed to do lots more in the first trial to make a case for APIs being purely mechanical. Appeals are about errors in law, not in the case made by the party I agree with.

    --
    davecb@spamcop.net
  30. Re:Fingers Crossed! -- Hope Oracle stays win . by Aighearach · · Score: 2

    You've got some santorum between your teeth.

  31. Re:Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    > MySQL was bought by Oracle. Why would a "serious" database company tarnish their name with that?

    My first guess was, "to kill it."

    There was a while there after Microsoft bought FoxPro, where they sold both MS Access and FoxPro. Soon it was just MS Access.

  32. You mean all the same sentences in the whole book by raymorris · · Score: 1

    I'd love to find a law that lets Google win this. I haven't seen a good one yet. Maybe Congress could make a law about interoperability, if Congress can ever do their job.

    It's not one sentence. You can use one sentence from a book. You can't use thousands of sentences. And certainly not arranged in the same in the same chapters (objects).

    Google has all the same stuff, thousands of words, arranged in the same structure. We're not talking about two or three words like a song title, or a sentence. The Java API is thousands of words - a complete book. I can't think of any law that allows copying thousands of words, though I wish I could.

  33. Re:You mean all the same sentences in the whole bo by Anonymous Coward · · Score: 0

    It's not like using the sentences from a book, though. It's more like using the index of the book.

    An API is not software, and having a list of 1000s of functions does not copy those functions. The creative work is unviolated.

    Google indexes the web. I would hate to think that Google search might go away because the courts ruled that an index of copyrighted works violates the copyrights of those works!

  34. Re:Use Java? Then you deserve whatever happens. by Seven+Spirals · · Score: 2

    OK. I take it back. Only because BASIC stomps the dogshit out of Java.

  35. RIP Fuchsia by Anonymous Coward · · Score: 0

    Google is pretty confident in the outcome seeing as how they've all but aborted their hedge.

  36. Re:Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    > OK. I take it back. Only because BASIC stomps the dogshit out of Java.

    10 GOTO HELL

  37. Re:JHMFC. Overreact much? by phantomfive · · Score: 2

    I read the 21 relevant pages from Google's writ, and I'd say it'll be granted. The second half of it hinges on fair use, and it's a weaker argument. The first half is all about the disagreements among the circuit courts, and that always attracts the attention of the Supreme Court.

    Lawyers are trained to be convincing, and they are by tradition only giving one half of the case. Thus when you read one side's argument (or sit in court listening to one side's argument), it will usually sound convincing. To get a clear view, it is necessary to read both sides. Even better, read the judge's conclusion. But don't make your analysis based on only one side's lawyers. They are biased by design.

    --
    "First they came for the slanderers and i said nothing."
  38. Re:You mean all the same sentences in the whole bo by phantomfive · · Score: 1

    It's not one sentence. You can use one sentence from a book. You can't use thousands of sentences. And certainly not arranged in the same in the same chapters (objects).

    It can be fair use. To claim fair use, you need to consider all of the four factors. Copying a large portion doesn't prevent a use from being fair use.

    "Using most or all of a work does not bar a finding of fair use. It simply makes the third factor less favorable to the defendant." Wikipedia suggests copying entire TV shows (which is more than thousands of sentences) as an example that was ruled fair use.

    If you have time I strongly recommend reading the court's finding. It is clear and well reasoned.

    --
    "First they came for the slanderers and i said nothing."
  39. Re:You mean all the same sentences in the whole bo by Anonymous Coward · · Score: 0

    "Maybe Congress could make a law about interoperability"
    Leave Congress out of it. When is the last time that collection of fuckwits did anything right and helpful? If we are lucky the government shutdown will last so long that people will start wondering why we even need the government. All the critical functions are not effected by the current shutdown.

  40. What happens if Google Loses? by Anonymous Coward · · Score: 0

    Worst case is there will be a new *nix API developed to be Open. Means rewriting almost all software ever written.

    Much of this will be outsourced to India. Major stuff ups.

    Every software engineer should be hoping Oracle wins. We will be on the gravy train or years fixing up the mess.

  41. Software patents are fucking stupid by TiggertheMad · · Score: 1

    You don't understand their claims. At all.

    You are correct, and Jesus fucking Christ, why should he have to understand the cluster fuck of a situation this is? Copyright law should be pretty simple.

    This is what we get when we let a bunch of fucking lawyers start doing stupid shit like copyrighting code in the first place. Code is math and algorithms, period. You cannot copyright math. Additionally, why don't you have to release source code to secure a copyright? If you don't, then it is a trade secret that you are getting copyright protection for. The whole point of the system is creating something of value (not idiocy like one click purchase, that's the covered by the 'obvious to a professional' part of the deal), and then sharing the details with the public in exchange for a short term monopoly.

    If we keep going down this road, more and more really stupid shit like this will happen. Ban ALL software patents and end this madness.

    --

    HA! I just wasted some of your bandwidth with a frivolous sig!
    1. Re:Software patents are fucking stupid by Anonymous Coward · · Score: 0

      > Code is math and algorithms, period. You cannot copyright math.

      It's not that simple. Code is a complex and creative arrangement of math and algorithms. It is a 'text' every bit as much as a novel is.

      Your argument is like saying you can't copyright a novel because the dictionary is full of words that can't be copyrighted.

    2. Re:Software patents are fucking stupid by Anonymous Coward · · Score: 0

      "Patent" and "copyright" are not interchangeable. But thanks for playing.

  42. Interface copyright: WINE, ReactOS by iTrawl · · Score: 1

    If interfaces can be copyrighted then WINE and ReactOS are dead unless they receive the blessing of Microsoft.

    If WINE is dead, Steam on Linux is also dead.

    If interfaces can be copyrighted, the message then is: if it's not an ISO standard so similar, don't touch it.

    --
    "Everybody's naked underneath" -- The Doctor
    1. Re:Interface copyright: WINE, ReactOS by iTrawl · · Score: 1

      I remembered another one: Ndiswrapper. That implements Windows interfaces to make Windows WiFi drivers work on Linux when there's no native driver.

      --
      "Everybody's naked underneath" -- The Doctor
  43. Prepare popcorn for armageddon... by Anonymous Coward · · Score: 0

    If Google wins it's a win for the software world, if Google loses it will be mayhem the likes of which no one has ever seen. And yet amidst that chaos, Oracle will suffer tremendously (do they have the copyright on every API they've ever used in their commercial database ? I think not).
    If Google loses, the Supreme Court will have handed IBM (and who's bigger and has a longer computer history than them) a mace that will destroy the software world. Lay back and enjoy the destruction. From the ashes a new open source mouvement will emerge.

  44. Re:You mean all the same sentences in the whole bo by kingramon0 · · Score: 1

    A better analogy would be if you wrote a book. Then I wrote a book with a different book title, but used all the same chapter titles that you did. Except the actual content of each chapter is different from yours.

    Oracle is basically saying that writing a book with the same chapter titles is copyright infringement.

  45. Re:Fingers Crossed! -- Hope Oracle stays win . by Anonymous Coward · · Score: 0

    Fuck off, do nothing anglo bitch.

  46. Re:JHMFC. Overreact much? by Anonymous Coward · · Score: 0

    The GPLv2 makes no promises either. It is freely revocable by the grantor.

    Freesoftware people claim NOOOO LIES ARREST THIS MAN FOR UNLICENSED PRACTICE OF LAW!
    (OR DISBAR HIM!)

  47. Unfortunately they fail all four factors of fair u by raymorris · · Score: 1

    You're right the amount of copying isn't the only factor. The four factors are:

    the purpose and character of your use (is it commercial, transformative?)

    the nature of the copyrighted work

    the amount and substantiality of the portion taken

    the effect of the use upon the potential market for the original

    Google fails the first. It's commercial. Original Java is a programming API, Google's copy is a programming API; there is no transformation into something else.

    Google fails the second. There have been lots of programming languages. Google not only could have made their own language different from Java, but they HAVE since done so, while also publishing a copy of Java.

    Google fails the third factor. They copied thousands of lines

    Google fails the fourth factor. They wanted to license Java for Android and Oracle wanted to license it to them. Google basically decided to go ahead and use Java commercially, in the same way that Oracle intended to use it, and just not pay the license fee. Oracle was trying to sell Java for phones via other avenues as well.

  48. You're right about that by raymorris · · Score: 1

    You're correct, you don't understand. First, copyright and patent are two different things.

    Second, what you can't patent is the laws of nature, including the laws of physics and the laws of mathematics. So you can't patent gravity - you CAN patent an elevator, which uses the laws of physics. You can't patent " x+y = y + x", you can patent machines that use gears and levers (which are multiplication). Java is not a law of nature. In fact in may be an abomination of nature. :)

  49. The GPL is not a contract. by Anonymous Coward · · Score: 0

    Thank you for the response, though I feel you don't address my
    question. Happily though, I spoke with an acquaintance and it was
    determined that the subservience to the license (i.e. agreeing to be
    bound by the GPL2) could not be offered as consideration as its
    restrictions were not the licensee's to offer at the time of
    acceptance of the license. The licensee had no rights to offer as part
    of the contract, as the contract had not yet given them any rights to
    give up. The terms put forth by the GPL2 are only restrictions that
    are part of the license.

    Furthermore, as stated above, it should seem quite self referential -
    I can't offer my acceptance of a license as consideration, because it
    is what I am trying to accept.

    As I am sure you are aware, under US law there is no contract if both
    sides have not provided consideration. This leaves us in the strange
    place of gratis licenses being suggestions.

    Cheers,
            R0b0t1

    1. Re:The GPL is not a contract. by Anonymous Coward · · Score: 0

      That's a dangerous conclusion which will get you into trouble.
      A license is a license, not a contract. Trying to treat the GPL or any similar license as "suggestion" will land you in court eventually, and you will lose.

      There are more than ample precedents for this! Why do you think the GPL has never really been tested in court, despite there being plenty of deep pocketed corporations around who would love to have it void and null?

      Because it's suicide to try to attack it, as you in the end are going to have to fight not the GPL itself, but the copyright law. Treating it as a "suggestion" is outright stupid, that's why. Everyone who has tried to challenge it in the end has settled out of court and mended their ways. You should make a special note of that. Everyone.

    2. Re:The GPL is not a contract. by Anonymous Coward · · Score: 0

      The quoted (r0b0t) is making the point that the grantor can revoke the GPL at any time. Indeed, it is not a contract. The licensee cannot "hold" the grantor to the "terms" (there are none: only instructions on how the grantor's property is to be treated) in the US.

      >"A license is a license, not a contract."
      Absolutely, a bare license is simply a license. That really is the point of the discussion.

      It is something many people do not understand: if the gratis licensor wishes to rescind at any time, he can. "Retroactively" (meaning you can no longer distribute the "already GPL'd" work). There are no binding contractual obligations on the part of the licensee. No consideration. No contract.

  50. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  51. Re:Prepare popcorn for armageddon...hope they deny by Anonymous Coward · · Score: 0

    Would be nice to see the industry where women rule over the men who actually do the work, fall in the USA.

    "Thanks for all your free work linux mmmaaallleeesss, here's a CoC and some punishment if you disobey us!" ..

  52. "in the Java language" by raymorris · · Score: 1

    Google is mistating merger.

    Walker v. Time Life Films, Inc., 784 F.2d 44 (2d Cir. 1986), is a great example of merger. It was a movie about cops in the South Bronx. Like another movie about cops in the South Bronx, "the scenery would include drunks, stripped cars, prostitutes, and rats." That's not a copyright violation, the court ruled, because ANY MOVIE about Bronx cops would have those sorts of things.

    What's not protectable are elements that EVERY WORK in the genre tend to have. Space movies have laser weapons, and spaceships which inexplicably have wings.

    Computer languages have functions like copying a string, which may be called copy, strcpy, strncpy, string.Copy, or just "=". Merger says can't complain that another language, much like yours, has string copy, because that's part and parcel of writing a programming language - they all have that, it's needed.

    You said "In the Java language, there is only one way to declare a function". The key words there are "in the Java language". In other words, "if you're making an exact copy of Java ...". Google has no inherent right to make and sell a copy of Java.

    Merger would apply if you could say "the only way to make a programming language is to ...". We know that making a programming language doesn't require duplicating Java (from the users' point of view), but most languages don't. Most programming languages do a lot different, a lot smaller, and a lot better.

    When Google says "in the Java language there is only one way", what Google is really saying is "the only way to copy Java is to copy Java". Well it doesn't work that way.

    1. Re:"in the Java language" by tricorn · · Score: 1

      No, you're describing scenes a faire, which is related but different.

      Oracle agreed in court that Google can freely use the Java language. That was not part of this case. Google's bytecode interpreter was not accused off copyright infringement. There were some patent issues, but those were resolved in Google'a favor.

      The only other issue was the Java API, and in particular, the names. Are the names part if the unprotected functionality in the Java API?

      "Authorship", which is what you can copyright, is predicated on choice. Choosing to write a program in Java is not a copyrightable choice Having made that one choice, the declarations for the Java API now can only be written one way.

      102(b) excludes "systems" and "methods of operation" from copyright protection. If the Java API itself (the abstraction, apart from any specific description) is a "system or method of operation", then the declarations merge with that and are themselves excluded from copyright protection.

    2. Re:"in the Java language" by raymorris · · Score: 1

      > Choosing to write a program in Java is not a copyrightable choice Having made that one choice, the declarations for the Java API now can only be written one way.

      Writing a program *in* Java doesn't require you to implement Java the Java API.
      Writing a program that *is* Java requires implementing Java API.

      They are allowed to USE Java. It does not follow that they are allowed to BE Java. I can distribute write a program that USES Windows, that doesn't mean I can distribute a CD that IS Windows or that looks and acts exactly like Windows, so it is Windows as far as anyone can tell, or that I can distribute Linux without following the GPL just because I can distribute a program that runs on Linux.

      Google / you are conflating writing an application FOR Java with writing an implementation of Java, an exact copy of its external appearance.

      What do you think of this. I create a space movie with Han Solo and Yoda, but I implement the characters with CGI, rather than with actors? Does it matter if I implement them with actors or with CGI?

    3. Re:"in the Java language" by Anonymous Coward · · Score: 0

      I can distribute write a program that USES Windows, that doesn't mean I can distribute a CD that IS Windows or that looks and acts exactly like Windows, so it is Windows as far as anyone can tell

      Isn't that ReactOS?

    4. Re:"in the Java language" by tricorn · · Score: 1

      If the Java API is a "system or method of operation", and is excluded from copyright protection by 102(b), why wouldn't I be allowed to re-implement the Java API if I want to?

      If I rewrite Linux from scratch, without copying any source code, copying only the functional requirements, I won't be infringing even if I ignore the GPL.

      If you make a movie with the characters Han Solo and Yoda from Star Wars, you'd be infringing on the copyrights on those two characters. They are not excluded from copyright protection by 102(b). It wouldn't matter if you used real actors or virtual actors.

  53. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    And yet, at the end, MySQL was just about the only thing actually making any money for Sun.

  54. Let's try a Star Wars analogy by raymorris · · Score: 1

    Let's try looking at this from another angle.
    I have a right to make a space fighting movie. The general idea used in Star Trek, Stars Wars, etc isn't copyright protected. What is protected is the storyline, the particular collection of characters, character names, catch phrases, etc. So let's try translating what you wrote to such a situation. You said:

    --
    Google's claim is that the abstract Java API is a "system or method of operation", and that it includes the specific names as part of that.
    --

    Do I have the right to use the specific names of Star Wars characters such Yoda, Han Solo, Princess Leia, etc in my space movie, because all of the character names are part of the idea of a space movie? Obviously not. I can make a movie about space, I can have a hero. I can't name my here Han Solo.

    1. Re:Let's try a Star Wars analogy by tricorn · · Score: 1

      The names are not copyrighted, though the characters are, and the names can be trademarked.

  55. Re: Use Java? Then you deserve whatever happens. by Anonymous Coward · · Score: 0

    Liar, liar, pants on fire.

  56. Re: Unfortunately they fail all four factors of fa by phantomfive · · Score: 1

    Yeah that's a more realistic analysis. The court decided the second factor in favor of Google though. It's an interesting read, even though it is long. I strongly suggest reading the decision.

    --
    "First they came for the slanderers and i said nothing."
  57. Do SC justices need technical expertese? by unixisc · · Score: 1

    Not just that, both companies are Left leaning companies. So even assuming that the justices would be biased towards entities that are pro Republican (not that it means much these days), they'd have little to choose from in this particular case.

    The thing that's interesting is - how much of tech expertise do these justices need? Obviously, none of them know the first thing about coding. So the most I can assume is that the plaintiffs would have to highlight high level of appropriation in order to make the justices even begin to understand the issues at stake. But when those concepts are at that high a level, chances are that they encapsulate extremely broad concepts (kinda like Amazon's one button shopping), enabling industry-wide monopolies. From what I understand, the root of Google-Oracle's dispute is the Java VM. While Snoracle's VM was essentially memory based, Google's is register based. Would that not be significant enough a departure for Google to have made from Oracle, since it would have required some significant code re-writing to pull that off? Or would simply changing the memory mode that the VM operates in be inadequate a change? And most importantly, are the likes of Sotomeyer or Gorsuch or Roberts gonna grasp any of that?

    1. Re:Do SC justices need technical expertese? by Anonymous Coward · · Score: 0

      From what I understand, the root of Google-Oracle's dispute is the Java VM.

      Your understanding is incorrect. The root of the dispute is Google's use of the copyrighted Java API. Oracle claims copyright on the code that declares Java's basic classes and their methods. The fact that Google compiles the code into binaries that run on a completely different VM is irrelevant.

      It had long been assumed that such code was not copyrightable, because it was purely functional. Oracle has successfully (unfortunately!) argued that the API code does contain an expressive element and is copyrightable. Google then countered that even if the API code was copyrighted, they should be allowed to copy it as a "fair use".

  58. Re:Fingers Crossed! -- Hope Oracle stays win . by unixisc · · Score: 1

    Nice trolling, but even if Linux were to die, there are still the BSDs that are available. Besides, Google has been looking more at the BSDs since their license is more compatible w/ what they need, and so have the other major companies. Also, is GPL 2.0 revokable? Even the FSF and Stallman haven't tried it, as that would end 99% of the GPL market - namely Linux.

    Maybe they should seriously resume work on the HURD?

  59. DAF the lot of it by Anonymous Coward · · Score: 0

    This is totally dumb. This is like saying the first implementation of an index, foreword, glossary etc for books can actually be copyrightable and that all books that implement it are in violation.

    As far as computing goes, names of methods, functions, API's, control flow etc are really just implementations of things that occur in real life for automation.

    Over the years it has boggled my mind how companies can use everyday words as their brand name and hence can shutdown legitimate usages of the object itself, such as apple, acorn, bell etc.

    The world has gone bonkers.

  60. Re:Unfortunately they fail all four factors of fai by UnderCoverPenguin · · Score: 1

    Original Java is a programming API

    Java is a programming language

    The API (actually APIs, there are many) is a list of function/method names and types, and their parameter names and types.

    Oracle's claims are that copying the text describing the API is copyrighted and copying the description is not protected by fair use.

    Allegedly, Google distributed copies of the API description with the Android development kit.

    I suppose one possible alternative Google could have used was have their development kit installer automatically download and run the Java development kit installer.

    --
    Don't try to out wierd me, three-eyes. I get stranger things than you, free with my breakfast cereal. --Zaphod Beeblebr
  61. Re:You mean all the same sentences in the whole bo by Shaitan · · Score: 1

    The problem is that software falls in this grey area between discovery, invention, and creative work. However, the creative work aspect is weak despite the code as art examples because you can make an artistic toaster without toasters generally falling under copyright.

    Being what it is functionally, an API should not be copyright-able and neither should software. Most software shouldn't be patent-able either. Very little is actually inventive and most algorithms are better argued as a discovery than an invention. Complicated math was true before you stumbled on it and the same is true of algorithms. None-the-less I doubt that is what the court will rule.

  62. Re: Use Java? Then you deserve whatever happens. by Shaitan · · Score: 1

    Which was actually a great way to get acquired by Oracle and make money for shareholders. Mission accomplished.

  63. Re:Use Java? Then you deserve whatever happens. by Shaitan · · Score: 1

    Java is slow and shitty, software written in it almost always leaks and it's a nightmare to support.

    Do you know why people use java? Because schools were obsessed with teaching java.

  64. Thanks for the link, btw. by raymorris · · Score: 1

    Btw thanks for the link to whichever decision that is. I'll read through it a bit later. I take it that's a court that ruled in favor of Google. I'm curious to read that because while I *want* Google to win, I can't imagine how they can under current law.

    1. Re:Thanks for the link, btw. by phantomfive · · Score: 1

      I'll go farther than that haha. I don't even want Google to win. It's just two rich corporations deciding who owes who a few billion. No big deal.

      The real question is, can I do what I want to as a programmer, even with this decision? Turns out the answer is, yes. All APIs that I want to use come with a license, and there is an interoperability fair-use defense available when companies don't want things like Wine to exist.

      --
      "First they came for the slanderers and i said nothing."
  65. Microsoft discovered Windows? Created it by raymorris · · Score: 1

    I take it you're not a programmer, or not a very good one. There is a VAST difference between a very good programmer and a beginner - the problem does not in fact define how the solution must be written, and every programmer would write the same thing.

    Linux and Windows are vastly different because Microsoft didn't *discover* an operating system, they *created* one. (Somebody else created DOS). Creating new things is called being creative.

    > Complicated math was true before you stumbled on it and the same is true of algorithms.

    "The first search result should be Snopes" isn't a mathematical truth. It's not only not a mathematical truth, it's not even a truth, but an opinion, an editorial decision. Editorial opinions can be written using letters of the alphabet (which pre-existed!), and other characters on the keyboard such as "+" and âs. The fact that the concept of square root exists doesn't make it a mathematical fact that you should buy a stock when we the square root of the trading volume is greater than the CEO's age; that's an opinion. (A stupid opinion).

    The fact that algorithms can easily give dumb answers demonstrates that they aren't mathematical truth - because they aren't even truth, they are opinion.

  66. ReactOS needs 96 MB, so not like Windows :) by raymorris · · Score: 1

    ReactOS requires 96 MB, so I'm going to say it's not just like Windows. :)

    In fact, it was discovered that ReactOS developers copy/pasted code from Windows (via a disassembler), so indeed there are copyright concerns. Microsoft didn't care enough to even comment about it. Perhaps that was because ReactOS has dozens of users, but anyway Microsoft didn't indicate that they *care* about ReactOS doing blatant copyright violation, copy-pasting from Windows.

    If Google were making billions of dollars distributing ReactOS on Chromebooks (Winbooks), then I bet Microsoft would care, and a court could decide how much ReactOS infringes, and if any of that infringement is fair.

  67. The court mentioned that - Google makes their own by raymorris · · Score: 1

    The court actually brought that up. Google makes their own index of the web. if I were to steal a copy of Google's index and sell it, they may be able to sue me for copyright infringement.

    Google's index is fair use of the snippets they use, the court has ruled, because it's transformative. You make a web page about iPad repair, Google makes an index of the web. Their use of a snippet from your page doesn't replace your page, in fact it makes your page more valuable for having been indexed.

  68. I've read most of it by raymorris · · Score: 1

    I've read most of the opinion (ruling) and so far it's page after page of why Google should lose. I was thinking you had linked to a ruling FOR Google. I kinda want to skip to the the ruling to find out, but I kinda like the suspense too. :)

    This ruling could affect interoperability, which is why I'd like to see Google win, but I don't think current law is in their side. I may come across a solid argument of why the law is on the side, but I haven't yet.

    So far I've come across why the law *should* allow it (why someone wishes it lawful), and people repeating Google's very flawed arguments, arguments that very clearly misstate the law.

    1. Re:I've read most of it by phantomfive · · Score: 1
      The argument in favor of Google is entirely in the second factor. You can skip through the ruling to that point if you want.

      This ruling could affect interoperability, which is why I'd like to see Google win, but I don't think current law is in their side. I may come across a solid argument of why the law is on the side

      The law isn't on Google's side on this one. The court addressed interoperability in the ruling, you can search for interoperability to find it. I would tell you, but why ruin the surprise?

      Interoperability is a valid fair use defense, though: see Sega vs Accolade. Another potential interoperability defense is that the functional parts of the code can't be copyrighted, only the creative parts (like variable names, how the library is organized). If I write software that interacts with Bitkeeper without looking at the code, merely looking at the protocol output, then there is a strong case that most of what I have copied is functional.

      Another novel item in this case, I think worth a look, is the way the court balanced out the four fair-use factors, in the conclusion.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:I've read most of it by raymorris · · Score: 1

      I went ahead and read the rest of it.

      Note in Sega they copied a few bytes. That was important. Interoperability is a consideration, but the case should not be read to mean that you can do whatever you want for interoperability. Sega held that you can copy a few bytes of functional code for interoperability.

    3. Re:I've read most of it by phantomfive · · Score: 1

      Interoperability is a consideration, but the case should not be read to mean that you can do whatever you want for interoperability.

      Yes. Quantity is a factor also, but it is the third factor, and needs to be taken into consideration. If quantity were the only thing weighing against Google, and the other three factors favored Google, then would they have lost?

      But actually three factors weighed against Google, and only one favored Google. And it is hard to justify that Google's use served the purpose of having copyright: to encourage the creation of art and culture by rewarding authors and artists with a set of exclusive rights

      --
      "First they came for the slanderers and i said nothing."
  69. Re:I hope Oracle wins for the wrong reasons by Anonymous Coward · · Score: 0

    Sounds to me like Oracle is f**ked no matter what.

    CAPTCHA: fetish

    That's my fetish.

  70. Re:Fingers Crossed! -- Hope Oracle stays win . by Anonymous Coward · · Score: 0

    " Also, is GPL 2.0 revokable? Even the FSF and Stallman haven't tried it, as that would end 99% of the GPL market - namely Linux."

    In the USA, yes. A license without an attached interest(usually $$) is revocable.

    That is why the FSF has always required copyright assignments for those who wish to contribute to it's projects (and other large OSS projects do the same (but not linux))

  71. Re:Use Java? Then you deserve whatever happens. by Seven+Spirals · · Score: 1

    Found the Java coder.