What does this mean for android?
If the White House position is successful, it means Android as open source software is finished. It may go on as proprietary, maybe. It also means SQL, C, C++, POSIX, and more stuff that I can count are forbiden land for open source, and every company making products that include or derivate from them own a non-negotiable unknow amount to some party.
White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
91–100 of 165 posts
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#92Earlier quoted context omitted.
Con: all the BSDs and Linux are now owned by whoever most recently picked up the POSIX APIs. ReactOS and WINE are now illegal. SQL is the private property of IBM. Pro: I guess if you hate Google because you love Steve Jobs or something it looks like a win.
Quick question - do you feel the need to associate this to Apple because of your deep personal hatred for that company, or for your deep abiding love for Google? Or was it neither, and you just like using rhetorical devices to bolster your weak points?
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#93On the one hand, this would have serious implications for compatible FOSS reimplementations of proprietary APIs, such as Wine, libc, emulators, etc. On the other hand, this would make it far easier to enforce copyleft licenses like the GPL. I'm one of the people who provided text and examples filed in the EFF's amicus brief against, and on balance I'm not a fan of stricter copyright like this, but it's interesting to…
Emulators are a tricky one because they often require a BIOS file which does break copyright.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#94Earlier quoted context omitted.
I'd be curious to hear RMS's stance on the issue, but I'm guessing he would agree with Oracle. http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/doc/Why-...
That's not the same issue. He's talking about distributing code that is not functional unless linked with a GPL library. Not about distributing code that replaces such GPL library. Oracle is basically saying that you can not write a compatible implementation of Java.
> I built a libnoreadline.a that can be linked together with lisp.a, replacing libreadline.a .
> I will reorganize the distribution into 2 independent parts: > * clisp.lzh containing lisp.a and libnoreadline.a, > * readline.tar.Z containing libreadline.a and its source.
> The first one is enough to build a CLISP executable. It contains no GNU parts.
If readline's API were copyrighted and unreimplementable, this would still be infringement. However, this is not actually the argument rms used; rather, he said:
> The FSF position would be that this is still one program, which has only been disguised as two. The reason it is still one program is that the one part clearly shows the intention for incorporation of the other part.
Who knows whether that would hold up in court or not.
Incidentally, these days (well, since 1997 or so?) we have editline, which, rather than being a sort of low-effort dummy implementation like the proposed "libnoreadline", is a full-fledged BSD-licensed readline replacement which provides a readline compatibility API. One possible outcome of this case, in which Google loses on both copyrightability and fair use, would make it arguable (not certain - Java is much larger than readline) that editline is infringing the GPL, which would be amusing.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#95Earlier quoted context omitted.
I'd be curious to hear RMS's stance on the issue, but I'm guessing he would agree with Oracle. http://clisp.cvs.sourceforge.net/viewvc/clisp/clisp/doc/Why-...
Very interesting link, thanks for sharing. From reading that, you can be near certain that RMS would agree.
And the terminology has improved greatly since then; for instance, nowadays the requirement would be described as making CLISP "GPL-compatible", rather than putting it under the GPL.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#96Earlier quoted context omitted.
The case doesn't touch patent law in the slightest, if I understand it correctly, though. (I am not saying the DoJ opinion is good in any regards whatsoever, to be clear)
No, but it adds copyright trolls to the mix. At least you can count on patents to expire eventually, copyrights are forever in software years.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#97Earlier quoted context omitted.
Emulators are a tricky one because they often require a BIOS file which does break copyright.
No more so than the games, and some emulators have reimplemented BIOSes.
It goes without saying that copying games is illegal. Well, bar a few caveats which seldom apply to people who run emulators.
> some emulators have reimplemented BIOSes
I'm sure some do but many don't - hence my point.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#98Earlier quoted context omitted.
The case doesn't touch patent law in the slightest, if I understand it correctly, though. (I am not saying the DoJ opinion is good in any regards whatsoever, to be clear)
No, but it adds copyright trolls to the mix. At least you can count on patents to expire eventually, copyrights are forever in software years.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#99Silly question. Is there any potential for Google to move off of Java (perhaps to Go) for Android development as a result of this?
Seems unlikely, since the article mentions that Google has already stopped using the code in question.
Re: White House Sides with Oracle, Tells Supreme Court APIs Are Copyrightable
#100Programming is in this odd position somewhere between the structure of math and the creativity of writing. Some things feel as obvious as basic addition, which clearly should not be copyrightable, while other things feel as clever as complex poems, which clearly should be copyrightable. I am not a copyright expert, but in my opinion APIs usually fall closer to the structured math half of programming. ex. GET, POST, P…
But, there seems to be a balance, is the API of a single class copyrightable? No, probably not. Is the API of a large system like Java's copyrightable, I really do think so.
Having said that, I disagree with the protections an API suddenly gains once we say I have a monopoly on its use and license. E.g. This verdict likely just made every emulator an act of copyright infringement. Does intel own the API on the x86 instruction API and can lock out AMD?