News for hackers. Stuff that matters.
Re:Oracle v. Google - What's The Deal With The Java Specific... by pron on Thursday April 19, 2012 @04:36AM (#3861966)
It's not the language that they took, but the whole platform. They don't provide a compiler from Java to whatever bytecode Dalvik is using, but from Java bytecode to Dalvik bytecode.

Now I'm not saying they're doing anything illegal or in breach of any contract - I really don't know - and I don't know whether or not you could own a language in the legal sense - I have no idea about that either - but all of Google's actions seem to be in bad faith.

Whether or not it has any legal merit, the Java licensing was specifically meant to ensure compliant implementations. In addition, Sun didn't want other mobile implementations and tried to prevent that. Then Google went ahead, forked Java into a non-compliant implementation (and that would have been fine, too), but built their entire tool system in such a way as to allow many compiled Java libraries to run unmodified on an inferior JVM - sorry, a 'non-Java' VM - that they'd bought with the sole intention of circumventing Sun's licensing.

I don't know if Sun had a right to license Java as they did, and I don't know if Google did anything legally wrong. But what is clear that they've tried to stay as close as possible to Java (the whole platform - not just the language) without breaching the letter of the law in Sun's license. In fact, most of their technical effort was directed at precisely that - circumventing Java's licensing.

Now, I don't know why people are rushing for Google's defense as if they've been acting altruistically or something. Everything the did, or do, they do for profit.

There are no good guys in this story. There are simply two huge conglomerates in a business war. Oracle is trying to take advantage of Android's success where they've failed in the mobile arena, and Google is trying to take advantage of Java's popularity. Both companies are simply trying to exploit each other for their own benefit.

Whatever the legal outcome, I think both developers and consumers would benefit greatly if Android were to become a compliant Java implementation, and could take advantage of Oracle's superior VM.

Re:Oracle v. Google - What's The Deal With The Java Specific... by chc on Thursday April 19, 2012 @03:03PM (#3864572)
Your only accusation of wrongdoing (either ethical or legal) seems to be that Google "acted in bad faith," but I have no idea what you mean by that. I believe that phrase normally means "used deception and subterfuge," but I don't see how Google did anything duplicitous.

You seem to think I'm "rushing to Google's defense as if they've been acting altruistically". This is incorrect. I don't know what your motivation is here, but I don't really have strong feelings about Google one way or the other. I'm just calling 'em as I see 'em.

All Google did is create its own implementation of a programming language. Never before in history has this been considered an evil thing. It happens all the time. I wouldn't call Rich Hickey or Guy Steele evil for "stealing" Lisp from John McCarthy, so out of consistency, I can't call Google evil for doing the same thing with Java. I also don't see how Google was deceitful in this, as you claim. They seem to have been quite up-front about what they were doing.

In fact, I'll go further: If any party acted in bad faith, it would have to be Oracle, which supported Google and Apache's alternative Java implementations up until it sued Google and gave Apache the middle finger.

Re:Oracle v. Google - What's The Deal With The Java Specific... by pron on Friday April 20, 2012 @08:09AM (#3867495)
Google did not just implement the language. In fact, they didn't implement the language at all: to the best of my knowledge they haven't even written a Java compiler.

All they did was write a translation tool that takes Java binaries and makes them run on a different VM, not covered by the Java license. Unlike others who implement languages to provide technical benefits, Google had no such intention. Their only consideration when choosing to re-implement a piece of Java or not was whether it would allow them to evade Java's legal restrictions.

My stake in this is that as a Java/other-JVM-languages developer, I don't like the fact that we now have two incompatible Javas. Now, Google explain their actions by saying that Sun were dragging their feet during negotiations, and maybe they're right. Maybe, thanks to Google we have an almost-Java thingy on a successful mobile platform.

I think the parties should settle, and I hope the result (whether money changes hands or not) would be bringing Android in the Java fold, and making it compatible.