Linked by Thom Holwerda on Fri 13th Apr 2012 09:40 UTC
Legal "Oracle's case against Google has evolved primarily into a copyright infringement suit over the past several months, and with the full trial scheduled to begin this coming Monday, the court is making an effort to get down to the nuts and bolts of copyright law. The judge issued an order last week requiring that both Google and Oracle provide their respective positions on a fundamental issue in the case: 'Each side shall take a firm yes or no position on whether computer programming languages are copyrightable'." Seems like an easy enough answer to me, especially since Oracle's example doesn't hold up at all - Oracle points to Klingon's custom glyphs to illustrate that a language can fall under copyright, but unlike Klingon, a programming language uses standard glyphs we all use every day. Arguing you can copyright that is borderline psychotic, and opens up a whole can of worms.
Permalink for comment 514067
To read all comments associated with this story, please click here.
RE: Programming in Klingon
by acobar on Fri 13th Apr 2012 15:12 UTC in reply to "Programming in Klingon"
Member since:

Joking aside, programming languages are not native languages. They do not spring up from a collective effort. It takes somebody, or a team of somebodies, a long time to author the grammar that defines a language. That grammar is a set, defined written thing, just like a book or article. This sounds like it could be copyrighted and entitled to copyright protection.

Oh, yeh, because Java structure, grammar and syntax is so different from everything that predates it and it encompass new symbols and words not seem before. Not!

Further, even if the base grammar isn't copyrightable, what about all those standard libraries that come with the language by default. ...

Like the IO? Or the Math?

Oracle argues that Google copies quite a few of the base libraries too. It seems like Google is arguing that the standard default libraries are not copyrightable either. Honestly, Google seems to have the weaker argument.

Keep in mind that many parts of Java were released under an open source license or were published under a standard body to everyone see. This greatly lower their instances. The interface was made public, not the implementation. To me it is like publishing what is in your recipe to cook something, without telling how to do so. Google did not copied the implementation, what could bring copyright issues, just used the same name, arguments and, possibly, issued the expected results on code return, what is the sane thing to do if you want to keep interoperability.

I disagree with your stance about Google having weaker arguments, but, as we all know, our law system is not about what is reasonable but, instead, about what is set on letters. It is a common mistake to think that the Justice System is about to be fair, one that is repeated by judges and lawyers to further the authority of the decisions achieved, it is a myth.

I really hope Oracle get what they deserve: a huge bill on legal costs and nothing more.

The lawyers, though, will get paid anyway, unluckily.

Reply Parent Score: 4