{"id":6734,"date":"2019-11-16T18:11:11","date_gmt":"2019-11-16T18:11:11","guid":{"rendered":"https:\/\/gtechbooster.com\/?p=6734"},"modified":"2023-04-01T01:36:48","modified_gmt":"2023-04-01T01:36:48","slug":"the-fate-of-programming-hanging","status":"publish","type":"post","link":"https:\/\/gtechbooster.com\/the-fate-of-programming-hanging\/","title":{"rendered":"The Fate Of Programming hanging"},"content":{"rendered":"\n

In an unexpected turn of events, the U.S. Supreme Court has agreed to hear Google’s petition asking for a judicial review of the copyright issues stemming from the Oracle v Google lawsuit. This will impact the future not only of Android but software in general. <\/p>\n\n\n\n

\"\"<\/a><\/div><\/div>

The Android issue has been hanging over us for nearly a decade and \nthere is some relief in thinking that the matter could be settled once \nand for all. But if the Supreme Court isn’t swayed by arguments set out \nin the Amicus Brief of 78 computer scientists it isn’t just Google and \nAndroid that will face penalties, the very foundations on which software\n is built will be impacted and code everywhere will be open to attack \nfrom copyright trolls.<\/p>\n\n\n\n

In 2010, when Oracle initially sued Google over the use of Java in the Android operating system, we thought it could spell doom for Android, and that seemed bad enough. Once the issue was widened to the question of whether APIs are copyrightable, the stakes became much higher and success for Oracle in the lawsuit could threaten the fundamental premise on which software is developed – that existing APIs can be used in new and novel implementations.<\/p>\n\n\n\n

To recap of the story so far, the case concerns 11,500 lines of code \nthat Google is accused of copying from Java in the pre-Oracle era. In \nJune 2012, U.S. District Judge William Alsup, who heard the case in \nthe Northern District of California ruled that the code in question was \nso trivial that it was uncopyrightable.<\/p>\n\n\n\n

This decision was reversed in May 2014 by a three-judge panel  of the United States Court of Appeals for the Federal Circuit. At this point Google petitioned the US Supreme Court to hear the case to settle the issue of copyrightability. The petition was supported by an Amicus Brief filed by the Electronic Frontier Foundation on behalf of 77 computer scientists which urged the Supreme Court  to overturn the finding that APIs are copyrightable.<\/p>\n\n\n\n

After seeking  the advice of the Obama administration, which indicated the view that APIs are copyrightable the Supreme Court accepted the Solicitor General’s recommendation not to re-open the debate and denied to hear the petition and sent the case back to Federal circuit. <\/p>

\"\"<\/a><\/div><\/div>\n\n\n\n

This led to a repeat scenario. In the second jury trial in May 2016, again heard in the Northern District of California by Judge Alsop the verdict was that Google’s use of the 37 Java APIs constituted “fair use”. This was then overturned in March 2018  by the U.S. Court of Appeals for the Federal Circuit in Washington with the same three judges who had found in Oracle’s favour in 2014 determining again that Google infringed copyright law in using Oracle’s software code. <\/p>\n\n\n\n

In January 2019 Google petitioned the Supreme Court to review the decision. This was supported not by the Amicus Brief filed on behalf of 78 computer scientists by the Electronic Frontier Foundation (which is the one that is to be considered by the Supreme Court) but also ones from Microsoft and from a group comprising Mozilla, Mapbox, Medium, Patreon, Etsy and the Wikimedia Foundation. <\/p>\n\n\n\n

Yesterday’s court order that Google’s Petition of a Writ of Certiorari and the supporting Amicus Brief are to be heard by the Supreme Court comes as a surprise in view of the fact that the Solicitor General, this time the Trump administration had again advised against this course of action. <\/p>\n\n\n\n

The Supreme Court hasn’t yet announced when the hearing will take \nplace but it is likely to be  during the current court session with a \nruling expected by the end of June 2020. <\/p>\n\n\n\n

This hearing will have ramifications for every company and individual\n who produces code – not just Android and Java code but all code. We \nreally do have to hope that the Supreme Court judges who assemble to \nhear the case have insights into what makes creating software a special \ncase – and not be treated as it is is poetry, drama or fiction. <\/p>\n\n\n\n

More Information<\/h2>\n\n\n\n