Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday January 14 2020, @05:15PM   Printer-friendly
from the #include⠀<stdio.h> dept.

The case Google v. Oracle America, previously named Oracle America, Inc. v. Google, Inc., is being heard by the US Supreme Court. At the center of the case is whether programmers require permission to use an application programming interface (API). The outcome will determine the extent to which APIs can or should be copyrighted. If it turns out that copyright can be used to lock competitors out of using any given API, then there are severe repercussions for software development, as all programs these days rely heavily on pre-existing libararies which are then accessed via APIs.

Google: The case for open innovation:

The Court will review whether copyright should extend to nuts-and-bolts software interfaces, and if so, whether it can be fair to use those interfaces to create new technologies, as the jury in this case found. Software interfaces are the access points that allow computer programs to connect to each other, like plugs and sockets. Imagine a world in which every time you went to a different building, you needed a different plug to fit the proprietary socket, and no one was allowed to create adapters.

This case will make a difference for everyone who touches technology—from startups to major tech platforms, software developers to product manufacturers, businesses to consumers—and we're pleased that many leading representatives of those groups will be filing their own briefs to support our position.

Mozilla: Competition and Innovation in Software Development Depend on a Supreme Court Reversal in Google v. Oracle:

At bottom in the case is the issue of whether copyright law bars the commonplace practice of software reimplementation, "[t]he process of writing new software to perform certain functions of a legacy product." (Google brief p.7) Here, Google had repurposed certain functional elements of Java SE (less that 0.5% of Java SE overall, according to Google's brief, p. 8) in its Android operating system for the sake of interoperability—enabling Java apps to work with Android and Android apps to work with Java, and enabling Java developers to build apps for both platforms without needing to learn the new conventions and structure of an entirely new platform.

Devclass: Google says nature of APIs under threat as Oracle case heads to US Supreme Court:

The case – ten years in making – centres on Oracle's claims that its Java patents and copyrights were infringed by Google when the search giant created its Android mobile operating system. An initial ruling in Google's favour was overturned on appeal, and the case is finally due to land in the Supreme Court this year. Google filed its opening brief for the justices this week.

When was the last time, outside of school, when you yourself have written a program entirely from scratch and not used even a single set of application programming interfaces? Yeah. Thought so.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Informative) by barbara hudson on Tuesday January 14 2020, @08:06PM (1 child)

    by barbara hudson (6443) <barbara.Jane.hudson@icloud.com> on Tuesday January 14 2020, @08:06PM (#943231) Journal
    AMD and intel had cross licenses, and after the agreement terminated, intel got caught flat footed with amd64 being better than their own, so had to get a license from amd to use amd64 instruction set.
    --
    SoylentNews is social media. Says so right in the slogan. Soylentnews is people, not tech.
    Starting Score:    1  point
    Moderation   +2  
       Informative=2, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 0) by Anonymous Coward on Friday January 17 2020, @05:24AM

    by Anonymous Coward on Friday January 17 2020, @05:24AM (#944425)

    However AMD stopped recieving access to new instructions when Intel MMX came out, since they were 'extensions' not part of the core x86 api. As a result AMD continued being able to use up to the PPro instructions, which fell under the existing license but not later multimedia instructions. This resulted in 3dnow and its derivatives up until the agreement was renegotiated with Intel around the time of SSE2 I believe it was. It set AMD back by years in multimedia performance and adoption of Intel's extensions were always much higher.

    They have continued pulling similar crap to this day.