Google Won't Beat Oracle

Oracle has got a lovely little document available right now that outlines their opening statements in their copyright infringement case against Google. As you can see, I've found this document hilarious on multiple levels, but also a bit sobering. Up until this point I haven't taken much time to really look at the dispute going on between Google and Oracle, because I've always considered Google as some unstoppable force of money and good PR. As I look at the details, though, it's becoming clear that Google is grasping for straws, and Oracle may have the upper hand in this case. To be clear, I'm still rooting for Google. Oracle quoted Andy Rubin in their opening statements:
"Finally, SUN has a different license for its library for SE and ME. The SE library is LGPL, ME library is GPL. That means anything that links with the ME library gets infected. And the SE library is not optimized for embedded systems. Sun chose GPL for this exact reason so that companies would need to come back to them and take a direct license and pay royalties.”
This is a pretty disgraceful way to use an open source license - OSS isn't about making a profit, it's about innovating as a developer community. Ironically, the same thing applies to the copyright and patent system that are now so abused. While Oracle may have very valid points in this lawsuit, I certainly believe Google is paving the road of innovation with Android, and will hold my respect whichever way the case goes. In case you're not familiar with the Google-vs-Oracle case, here's a bit of back story. Sun (now owned by Oracle) wrote an incredible piece of software called Java Runtime Environment (JRE), which is best known for its powerful Java Virtual Machine (JVM). The JVM allowed developers to write code in a single language and run it on any platform (coined "Write Once, Run Anywhere" by Sun). This was an incredible innovation, and added some great efficiencies for developers whose markets were cross platform. Along with the JVM, Java has another critical piece: the Java API. The API is the portion that is commonly (and somewhat incorrectly) called the Java programming language. In reality, the Java API is just like any other API - it's an interface supplied by Sun so that developers can interact with the JVM. In functionality, the Java API behaves quite similarly to a standard programming language, but differs in how it compiles. Standard languages like C compile down to assembly language, and is processed directly from there. Java, however, compiles down into a type of bytecode, and that bytecode is again compiled by a just-in-time complier built into the JVM. This is the crucial piece that makes Java an API, instead of a standard programming language. Java is just an interface which people can use to communicate with the JVM. This is Google's fatal flaw. Google is trying to argue with Oracle that they can't copyright a programming language. I believe they will successfully win that argument, and for good reason. Can you imagine a world where C could have been copyrighted? Unfortunately, Java is not a programming language. Java is an interface for interacting with a piece of software (the JVM). Google was intentional about not wording their argument as such, because I believe it's very clear that they could not win. Under that definition, there is an incredibly large amount of APIs out there that are necessarily copyrighted. Flip this on its head, and imagine if Google had to open up their Customer Search API. Not only would they lose one of their major revenue sources (because they couldn't license it), but their entire structure would break down because the world would have a clear view into how they score their search results. I guess at the end of the day I'm torn. Google is mostly in the right, here - they're using Java in an innovative way and they've created a wonderful developer platform with Android, but on the other hand they're clearly stealing.  I would hate to see Oracle win this case, because I believe they decrease the flexibility in the tech sector on many fronts, but I'm also afraid of the implications of APIs not being copyrightable.
Thanks for reading by . Want to read more?
comments powered by Disqus