3 ms·
What bad things would have happened? This ruling specifically says that it was fair use, not that APIs are copyrightable - which seems to be the buggy man. As i
by kaba0 6y ago
What bad things would have happened? This ruling specifically says that it was fair use, not that APIs are copyrightable - which seems to be the buggy man. As it currently stands, APIs absolutely fall under copyright laws.
- mindcrime 6y agoWhat bad things would have happened? It would have become MUCH more dangerous to provide an alternate implementation of someone else's library or interface, which I believe would have have a profoundly negative effect on the entire software industry. As it currently stands, APIs absolutely fall under copyright laws. Yes, but now there is a very strong precedent establishing the idea that copying those copyrighted API's is OK anyway (under Fair Use) under at least some circumstances. And based off the way the SCOTUS decision was worded, it strikes me (admittedly, IANAL) that the set of circumstances that are captured by this are pretty large.
- kaba0 6y agoIANAL, but it was always true that fair use made code exempt from copyright. Wine is alive specifically because of that.
- joshuamorton 6y agoThis case would have changed that has the rolling differed.
- curt15 6y ago>As it currently stands, APIs absolutely fall under copyright laws. This opinion doesn't say so. "We shall assume, but purely for argument’s sake, that the entire Sun Java API falls within the definition of that which can be copy-righted. We shall ask instead whether Google’s use of part of that API was a “fair use."
- kaba0 6y agoIt would be dumb to declare true the opponent’s case in the argument, wouldn’t it?
- UncleMeat 6y agoNo, it is a sidestep. Even if the code is copyrightable, it doesn't matter. The majority decided it was better to make a case for fair use than for the uncopyrightability of APIs. That's all.
- kaba0 6y agoMy understanding is that the original problem was that there is nothing in law that makes a difference between actual implementation code and API. Otherwise it would have been a trivial case. And even in this, they rather go with the easier fair use claim that is case-by-case.
- dkjaudyeqooe 6y agoOnce you use someone's API, then they dictate where and when your program works, unless you rewrite your program to not use that API. Given the countless and fundamental APIs that are typically used in any program, do you not think that is a Bad Thing? Given that most programmers have assumed that to not be the case, it would be very bad for existing code at the very least.
- kaba0 6y agoWell, if you are looking at an API which’s license explicitly forbids copying, I would stay away from copying it. While this case do give a precedent, it is much more about this specific case being a fair use according to the supreme court, than on whether APIs itself are copyrightable. Also, given most programmers’ assumptions, I would not base much on that alone :D But IANAL, so do ask one, to be safe.
- notriddle 6y agoIf Android Java was illegal, it seems likely that GNU, Wine, OpenStack, the Mastodon client API, LibreOffice Calc, ... this ruling is limited enough that some or all of those might still be illegal, but at least the open source clone of `windows.h` that winelib distributes is probably safe.