Keith Collins | Quartz | February 13, 2017 | 0 Comments

Oracle Has Now Spent Seven Years Claiming That Google Plagiarized its Code


Oracle filed yet another appeal yesterday (Feb.10) in its never-ending lawsuit accusing Google of stealing its code. Here’s a short recap of what got us to this point:

“When a plagiarist takes the most recognizable portions of a novel and adapts them into a film, the plagiarist commits the ‘classic’ unfair use,” attorney’s for Oracle wrote in its new brief. “No court would accept the defense, ‘I added other content and creativity to make the story work as a movie’ or ‘I transformed the story by adapting it to a different medium.'”

“Google reaped billions of dollars while leaving Oracle’s Java business in tatters,” the brief says.

The big question in this case has always been whether Google’s use of the code could be considered “fair use.” In copyright law, fair use means that the way in which the copyrighted work was used had no substantial negative impact on the copyright holder.

There are four criteria courts use to establish whether something is fair use, but this case has largely revolved around one in particular: whether Google’s use of the code had a negative effect on the market for Oracle’s Java API.

One jury has already decided that it did not, and another one believed the question itself was moot. Now, nearly seven years after filing its original suit, Oracle appears undeterred and hopeful that its third chance in court will be its charm.


Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.