Op-ed: Oracle Attorney Says Google's Court Victory Might Kill the GPL (arstechnica.com)
Annette Hurst, an attorney at Orrick, Herrington & Sutcliffe who represented Oracle in the recent Oracle v. Google trial, has written an opinion piece for Ars Technica in which she urges developers and creators to not celebrate Google's win in the hard-fought copyright case as the decision -- if remains intact -- is poised to make them "suffer" everywhere and also the free software movement itself "now faces substantial jeopardy." As you're aware, in a verdict earlier this week, a federal court announced that Google's Android operating system didn't infringe on Oracle-owned copyrights because its re-implementation of 37 Java APIs is protected by "fair use." Hurst writes: No business trying to commercialize software with any element of open software can afford to ignore this verdict. Dual licensing models are very common and have long depended upon a delicate balance between free use and commercial use. Royalties from licensed commercial exploitation fuel continued development and innovation of an open and free option. The balance depends upon adherence to the license restrictions in the open and free option. This jury's verdict suggests that such restrictions are now meaningless, since disregarding them is simply a matter of claiming "fair use." It is hard to see how GPL can survive such a result. In fact, it is hard to see how ownership of a copy of any software protected by copyright can survive this result. Software businesses now must accelerate their move to the cloud where everything can be controlled as a service rather than software. Consumers can expect to find decreasing options to own anything for themselves, decreasing options to control their data, decreasing options to protect their privacy.
"Best Sour Grapes of May 2016"
"Best Nail in Coffin for Confidence in Legal Judgement"
We know where leadership by an anti-intellectual "strongman" who scapegoats minorities and likes boisterous rallies goes
It's the implementations that they're protecting with the GPL, not the interfaces.
There never was copyright on the interface code as it is required to function. This was about Oracle bean counters trying to make their balance sheet look better through shenanigans rather than actually doing real work.
This case was not about the core code which is still covered fine by copyright and the GPL.
These comments are just spin.
Re-implementing an API and wholesale lifting a GPL software package are not even vaguely related. And, the end part of her quote, where she proclaims doom and gloom if we don't all move to the cloud, is ponderous hyperbole. The is just scare tactic garbage from an attorney who wants to bait the waters before she takes on the appeal and charges Oracle millions of dollars for the privilege.
Oracle's loss is a huge threat to free software and the GPL. That's why Stallman has been campaigning on their behalf for years now, hanging out with Ellison on his private catamaran, writing op-ed pieces supporting Oracle's treatment of Java post-Sun acquisition, etc.
I'd post the links, but it's easy enough to find them with Google.
Before Oracle v. Google, everyone assumed (based on extensive legal precedent) that APIs were not subject to copyright at all. Yet the GPL was just fine. Why would the GPL be threatened all of a sudden just because one more API turned out to be copyable?
The only tangible result of this case has been a very slight strengthening of copyrights, since the appeals court rules that APIs might be copyrightable under certain circumstances. How does strengthening copyright weaken a license that relies on copyright?
This is either monumental stupidity, or outright shilling. Hanlon's razor suggests I ought to go with the former, but I'm going to wait and see.
IBM's BIOS was not reverse engineered. The commented Assembly Language source code for the BIOS is published in the Technical Reference Manual which anybody could purchase.
Phoenix had to hire programmers to read the IBM source, write a human language specification, then hand that specification over to a seperate team to code their version of BIOS. Anybody on the first team, or anybody who had access to and read the published IBM source code was disqualified to work on the reimplementation.
In other words, IBM published their BIOS in commented human readable source code. The PC was in this regard among others, an open architecture.