Slashdot Mirror
US Justice Department Urges Supreme Court Not To Take Up Google v. Oracle
New submitter Areyoukiddingme writes: The Solicitor General of the Justice Department has filed a response to the US Supreme Court's solicitation of advice regarding the Google vs. Oracle ruling and subsequent overturning by the Federal Circuit. The response recommends that the Federal Circuit ruling stand, allowing Oracle to retain copyright to the Java API.
Sun was flush with cash at the time of the acquisition, and also had a great deal of solid IP and customer faith. Solaris prior to Oracle was *the* most solid OS available in my opinion, and sparcs were always great for their target audience. Sun's only problem is the market became too commodity - fabbers need to make billions of chips now to stay competitive, and that just wasn't possible. But Sun had paths forward to fix these things - they were actually on the right road already, imo - forming ties with AMD, coming up with a way to keep their core but become commodity, by giving AMD access to high tech they needed. A road that Oracle took them off - Sun would be just fine today if Oracle hadn't bought them.
If the laws we have now were in place back then the computer revolution wouldn't have happened. We would still be paying $5000 for IBM Mainframe access terminals.
Or in a slightly less Dystopian view, computers today would look like iPhones, with one vendor having a stranglehold on the platform and completely anemic third party hardware support outside of cosmetics.
I read the internet for the articles.
I believe it's not that you can't use the API, but that you can't interface non-GPL code with the kernel due to the restrictions of the GPL. That you would use the API to do so is incidental to that restriction.
If instead you want to build your own kernel implementing the same API, I don't believe they have any objection.
--- Most topics have many sides worth arguing, allow me to take one opposite you.
Google probably does copy/paste of the Java source code all the time, like lots of other people, because it's open source, so that is a meaningless accusation.
Google distributed interface definitions that look very similar to Oracle's. That's probably because in Java, there really aren't a lot of different ways of describing the same interface. Furthermore, interfaces should not usually be considered copyrightable.
Google also distributed some copyrighted Java source files. That was stupid, but those files appear to have been test cases, not code that ships on handsets, and it appears to have been unintentional. It's hard to argue that Oracle suffered any harm from that and Google came into compliance.
Or Google has been resisting the NSA a little too much.
This.
It's pretty obvious that this is a punishment for adding encryption to Android devices, and for going to SSL for all web transactions, making it much more difficult to spy, despite administrative objections.
The recommendation is clearly punitive because Google has pissed the executive off, and consistently opted on the side of data protection, and has disclosed many of the recently discovered OpenSSL and SSSL protocol flaws which made eavesdropping easier.