Oracle Vs. Google and the Right To Use APIs
jfruh writes "Even as an EU court rules that APIs can't be copyrighted, tech observers are waiting for the Oracle v. Google trial jury to rule on the same question under U.S. law. Blogger Brian Proffitt spoke with Groklaw's Pamela Jones on the issue, and her take is that a victory for Oracle would be bad news for developers. Essentially, Oracle is claiming that, while an individual API might not be copyrightable, the collection of APIs needed to use a language is. Such a decision would, among other things, make Java's open source nature essentially meaningless, and would have lots of implications for any programming language you can name."
What really reeks me is Google's double standards on these issues. Yes, APIs should not be copyrightable. But here we have a company that is trying to copyright search results listings. Listings that are built from other people's content!
I understand Google's need to protect their business, but the view they're trying to make of themselves is cowardly. Google wants everyone to look upon them as some kind of white knights and better-than-you company. Yet they do exactly the same thing when it's their business on the table.
It's not only some vague Terms of Service or other mainly uncontrolled and unforceable terms either. Google will ban you from accessing their service the instant their algorithm detects it's not an actual human being making searches and viewing their ads. Even if you behave nicely with your scripts and rate-limit them not to hit Google's servers badly. On the other hand, Google has no problem hitting your servers and causing more than $1000 fees for the owner for nothing.
Before Google starts attacking everyone else about these issues, maybe they should rethink their position. Otherwise it's just bullshit. And bad bullshit too, because they are trying to hide the fact.