† In the United States.
The apparent legal position following this result seems crazy to me. Even in the world of intellectual property law, there has been some recognition that the interests of interoperability and ability to communicate may outweigh the benefits of monopoly protection as an incentive to create and share. The US, for example, takes this view in declining copyright protection on the design of typefaces (as distinct from font files that contain software describing those designs in one specific way). And in Europe, good luck getting a software patent that blocks anyone from using your file format or communications protocol.
Given that programming to an interface is essentially the way we enable interoperability between different software products, allowing the protection of such interfaces to stand seems absurdly counter-productive. This is particularly true if the protection holds retrospectively for APIs that were previously believed not to be protected in that way by those who chose to write code against them, which would presumably be the case here.
If the US allows this position to remain, it could cripple the US software development industry very quickly if the lawyers start throwing their weight around. In practice, as often happens under the US legal system, I expect it would be particularly damaging to the little guy, while the big players would all cross-license their respective portfolios somehow to make the issue go away.
Which is funny, because Microsoft played a big role in helping Oracle win this one:
http://arstechnica.com/tech-policy/2013/02/microsoft-foresee...
Sure, as far as languages go, I there are many tasks more beneficial to the platform than changing its language, but the legal issues they are encountering sound like another good motivation.
invokedynamic is a bytecode. Not supporting it means Dalvik / ART can't accept valid bytecode.
> I think the lack of nio is an annoyance that can be fixed tho.
Apparently not. A quick check also suggests that ClassLoader#registerAsParallelCapable is missing.
When the Federal Circuit court overturned District Court's decision on the copyrightability of SSO, they remanded the issue of fair use back to the lower courts. After all, both Google and Oracle's goal through all this is not an academic exercise in establishing the general boundaries of copyright; their question is, "Are we/they going to have to pay in this case?".
Now, using a language which is owned by one company, Google's lawyers really dropped the ball in terms of risk.
I would say it's Google's executives and engineers who have dropped the ball if the moment Oracle won the case the last time, they didn't start planning and working on stripping Java out of Android. If they still have a "let's wait and see" attitude about it for another 2-3 years or how long these Court battles will take to settle, then THAT would be a major fail on their part. Because by then they would have to pay who knows how many billions of dollars and it would take yet a few more years (5+?) to do the whole transition.
It is prudent to note that Google didn't write its own implementation from scratch: they took advantage of Apache Harmony (by erstwhile Sun frenemy: IBM). This is the same Apache Harmony that Sun repeatedly refused to provide the TCK for
At that point, if SCOTUS does not take up an appeal, the computer science world will have a big problem. If APIs are copyrighted and reimplementing libraries violates copyright, then:
What of all the projects that have implemented LIBC, and used glibc's API and headers? e.g.: Is musl now GPL?
What of any OS or project that has implemented a POSIX layer? (Is this the decision SCO needed to finally sue someone for Linux finally violating SCO's copyright?)
What of any project that implements x-plat APIs? As another comment pointed out, Microsoft's Project Islandwood re-implements iOS APIs. But Xamarin, Cordova and other projects all ingest APIs and reconfigure them to make them accessible on multiple platforms. Are they contaminated by copyright now?
If the Federal Circuit decision stands, software might have finally encountered the lump it can't digest as it eats the world.