The Case For Oracle
An anonymous reader writes "In a lucid writeup, InfoWorld's Neil McAllister takes a different angle on the Oracle-Google lawsuit, giving an explanation why Oracle was right to sue Google. McAllister argues that Google is splintering the Java platform, just like Microsoft was doing back in the 90s, and should be held up to the same standards. He further cites Google's Josh Bloch calling for Oracle to take a lead role in steering Java, concluding that Bloch maybe 'should have been more careful what he wished for.'"
Java is their language. Don't like it? Don't use Java.
Myself, I never use Java because I don't like the language, that's my personal choice. But if Google wanted to use Java in a different way they should create their own derivative like Microsoft did with C#.
It feels kinda strange to defend Microsoft, but that's the way it is.
I don't know why anyone ever suggests this. It would be suicide for Google. The moment they revealed they would even consider blocking search terms in retaliation for anything they're no longer trustworthy as a search engine.
Google isn't advertising Android as a Java platform. It's a platform that you can write code for in the Java language, yes, but this is a world away from claiming you're shipping "Java", and virtually no end users are under the impression Java has anything to do with the Java platform. Be very clear about this: no applications shipped as .jar (or .class) files for J2ME, J2SE, or J2EE, will run under Android, and nobody thinks they will.
By comparison, Microsoft was shipping a supposedly compliant, but actually semi-incompatable, JVM with Windows that gave users and developers the idea it was a full implementation, which caused programs supposedly written for Java to often fail if either written for the Microsoft JVM and run under a standard stack, or vice versa.
If this is the crux of the author's argument, he's an idiot. If Google is "fragmenting" Java by allowing you to write programs in the language for its platform, then I suppose every operating system author, from Microsoft to Commodore, has been "fragmenting" Unix by allowing you to write code in C for their non-Unix operating systems.
You are not alone. This is not normal. None of this is normal.
McAllister argues that Google is splintering the Java platform, just like Microsoft was doing back in the 90s, and should be held up to the same standards.
What the hell does that mean? Microsoft got sued because it failed to live up to a contract (huge surprise there.) There are no contractual issues here, so far as I'm aware (if I'm wrong someone please correct me.)
Java isn't some religious manuscript that needs to be kept "pure" so the true believers won't rise up and slay those who would adulterate it. It's a goddamn PROGRAMMING LANGUAGE. If Oracle is suing Google, it has nothing whatsoever to do with Java being held to some standard (I could believe that of Sun, who held a certain vision for their progeny and a justifiable pride in their work) but is part of a some strategic plan. Matter of fact, that was Sun's strategy: keep Java consistent across all platforms so that "write once, run anywhere" would work. Do you really think that is a part of Oracle's planning? Is it even of the slightest concern?
Larry Ellison is a lot of things (I've heard appellations such as "real son of a bitch", "bastard", and "prick" applied to him on a regular basis) but he's not exactly a visionary. This is about money and access to specific markets, and trying to spin it as being about the welfare of the Java programming language is ridiculous. If I were a real conspiracy theorist I would have to wonder if one of Google's real competitors in the advertising space were behind this, but I'm not. I leave that to other posters.
The higher the technology, the sharper that two-edged sword.
I wish that I had mod points left. I would modded you up. The fact is, that if Google were to do what the GP did, well, that would make them JUST LIKE MS. That is why MS was sued, and lost. The last thing that Google needs to do is something that stupid. It helps in the short term, but kills in the long.
However, Google does not have to help Oracle either. And if I were Google, I would start exploring, along with the other phone companies, another VM. And let it slip that they are now exploring a different route for ALL OF THE SMART PHONES AND PHONES. At that point, Oracle will become VERY concerned about the idea of losing that market. Sun had the same issue. Wanted to make LOTS of money, and they were not content to simply control it as well as be the top money maker. They wanted the largest profits possible in the shortest time. That approach is what Oracle is doing.
I prefer the "u" in honour as it seems to be missing these days.
But hasn't Java been doing a good enough job splintering and fragmenting the platform with J2EE, J2SE, J2ME MIDP 1.0/2.0/3.0, JavaFX on its own?
http://twitter.com/object404
Block all searches for Oracle and Java on its search engine, until this issue is resolved
problem solved
Not really. Google is hardly the only search engine giant out there, and the ensuing public-relations disaster would be far worse than if Google ends up dropping Android entirely. Android is just an experiment for Google, a way to give more eyeballs access to its services (and hence advertising, which is where Google earns its revenue.) Granted, Google needs Android (or something like it) in order to continue its growth because the mobile market is enormous and growing exponentially, and it has heavy-duty competition that wants a slice. Either way, it wouldn't really be in Google's interests to try and play hardball there, especially since it would likely draw the attention of Federal regulators. I doubt they want that.
The higher the technology, the sharper that two-edged sword.
While I like to feel that Google is somehow better than Microsoft in all ways, I know this is clearly not true. The problem I do have with Google and their Java VM is that they aren't really contributing back to the core Java platform, and their choice of a different VM byte code makes me think of some of the things that hurt Smalltalk. In the case of Smalltalk none of the differing VM implementations were compatible, so it meant the you lost of the ability of 'compile once, run everywhere'. In many way what Oracle should be pushing for is:
- getting Google to use the standard Java byte code
- working with Oracle to contribute their work back to the core
J2ME is in many ways a dead platform, for GUI based devices, (at least, I am not aware of places proudly taking it forward), and Android is the best chance for seeing Java on low resource mobile platforms.
If Google does end up taking the same road as Microsoft with J++, then is could hurt very much what makes the Java appealing and even hurt the long term viability of Java as a cross-plaform language.
Jumpstart the tartan drive.
Face the truth why didn't Google use a full implementation of java as they are required by the patent grants. Because they wanted people to write for there platform and not simply port software. Just like Apple not wanting Flash for the same reason.
Actually there are a number of similarities. I'm not taking sides here - I don't write Java and don't care about it myself. However, I do care that licenses are upheld as I've personally been bitten by people ripping off my code for their profit.
When Google decided to use Java they had full access to the Java license, and they had full knowledge of the very public lawsuit between Sun and Microsoft. They still chose to do what Microsoft did and ship an incompatible version of Java. I suspect that (like Microsoft) they feel they are above the rules that govern other developers.
Google knew what they were doing. Why they did it, I don't know - did someone decide to ignore the license, or did they forget to involve the legal folks, or maybe they didn't think the license applied to them. The point is that they did use a great deal of the Java code, but then they discarded the bits and pieces that they didn't need. Can't blame them for that - why do work that you don't need to do. One answer: because the license says you must. Same with the executable format - you can come up with a better one, but it clearly breaks the Java license and the whole spirit of Java (as I understand it) if you make it the only way to execute code on your system.
I like Google, I really do. Google has done great things in the last few years, but they are starting to do some really boneheaded stuff also (net neutrality comes to mind immediately). Their corporate attitude seems to be "we're changing the world, get out of our way." Which is fine provided that you don't trample on other people and their rights in the process. I also worry about all the free stuff they give away - Microsoft used to do a bunch of free stuff in the early 80s, and look how that changed - will Google's shareholders eventually demand that they monetize everything?
I suspect this is just a ploy by Oracle to monetize Java by making Google pay for a new and special license for the Android platform. Nobody ever accused Oracle of being a philanthropic institution. I don't think this has any negative sides for FOSS - it's just a case of getting companies to follow the license that goes with the code they use, otherwise they have no license to use the code. It's no different than suing companies who don't follow the terms of the GPL license, and I don't see people up in arms about that.
One difference, Oracle has a pile of money and can afford to the best lawyering around. But so can Google. It will be interesting to see how this goes.
Face the truth why didn't Google use a full implementation of java as they are required by the patent grants. Because they wanted people to write for there platform and not simply port software.
Google didn't use a "full implementation of Java" because J2SE is extremely bloated and unsuitable for mobile phone use. And they couldn't use Sun's implementation because that wasn't even open sourced when they started. J2ME doesn't have a patent grant, so making a cleanroom implementation of that wouldn't have helped them either.
Of course, Google didn't use "an implementation of Java" at all, they implemented something completely different that happens to use Java syntax. Oracle's lawsuit is not based on the parts that Android happens to share with Java, because those are not covered by any patents.
Sorry for replying to self, but /. has no edit function...
The above "solutions" I suggest are solutions which keep Dalvik - I don't know why Google has chosen Dalvik over Java VM, I assume/hope it was on technical grounds. Dropping Dalvik, perhaps in favour of Java VM, might also be an option.
The only problem is that Dalvik ISN'T a JVM. Never was, never will be, and was never called one.
Whether or not SCO had a case for copyright infringement or not was never tested in court because it turned out that they did not in fact own the copyrights in question.
There was no infringement on SCO's copyright because SCO didn't have any copyrights infringed. There is no copyright infringement for SCO to have tested in court.
A fork is the best thing that could happen to the platform.
Are you sure? I remember way back in 1997, in school, writing apps with J++ and their were MS name spaces, and the documentation indicated that it was an Windows only function?
Some say this is only because Oracle now has Java, but if the issue is the mobile platform, we also see that Google is playing hardball with the phone. Google is suing companies that use Google tech on Android without Google approval. Google is charging $5 to play in the Chrome field. Google is clearly aggressively protecting it's IP. Not allowing Sun to do the same is hypocritical.
With a unified Java we have a language that one can do many interesting technical things in without a required $1000 IDE. The applications from Java is about the only thing that competes with MS and Adobe. Openoffice.org is one of the very few alternative we have to paying MS a huge amount of money or giving Google control over our data. Defending Java is a big deal. Taking it down would provide competitive advantages to many big players.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
Since Google never claimed it was Java
Maybe Google never formally said that, but here is how Wikipedia describes Android:
The Android operating system software stack consists of Java applications running on a Java based object oriented application framework on top of Java core libraries running on a Dalvik virtual machine featuring JIT compilation.
Even clearer, Google says
The Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.
in developer.android.com.
I suppose you can call it The-Language-Previously-Known-As-Java or such (worked for Prince, til his contract ran out), but it is Java in every way that counts, except it has some differences that make Java the platform as a whole less standard. This irked Sun, and for good reason, but they got over it. Oracle is not over it. Sadly they decided to enforce this using patents, which is an abhorrent thing to do. But that they are irked by Google's actions - very understandable.
The mods seem to be on crack today^H^H^H^H^H. The parent's suggestion might be misguided and would be harmful to Google's credibility (as several people have pointed out) but there is no reason to believe he's trying to provoke a fight or troll.
Flamebait != "I disagree"
Talking points:
See any difference?
And ye shall know the truth, and the truth shall make you free.
John 8:32(King James Version)
Maybe Google never formally said that, but here is how Wikipedia describes Android...
"Yeah, but Wikipedia's summary uses the word 'Java'" is an insightful argument? How Wikipedia describes Android has no bearing on this issue.
The Android SDK provides the tools and APIs necessary to begin developing applications on the Android platform using the Java programming language.
They built a clean-room implementation that uses Java bytecode created with your favorite Java IDE and compiler to produce their own unique Dalvik bytecode. They do not call it Java and they do not use Sun's JVM.
...but it is Java in every way that counts, except it has some differences that make Java the platform as a whole less standard.
No. Google capitalized on developers' familiarity with Java to avoid creating a new programming language and convincing people to learn it. The Java syntax is familiar and comfortable. However, Google is not calling these Java programs. A Dalvik app for Android is not going to run on a JVM. This is obvious to anyone developing for Android.
This irked Sun, and for good reason, but they got over it. Oracle is not over it. Sadly they decided to enforce this using patents, which is an abhorrent thing to do. But that they are irked by Google's actions - very understandable.
If you had bothered to follow this when it happened, read the history now, or even read the previous Slashdot stories recently, you would know how off-base your comments are. Negotiations between Sun and Google didn't go well, Sun's stock value plummeted, and Schwartz began shopping Sun soon after Android's debut. Oracle bought Sun with the intent of suing Google. Oracle took a calculated business risk by investing in a company with very little value in the hopes of cashing in on this lawsuit.
They decided to enforce this using patents because that is the only sliver of hope they have in this. Google was careful in how they approached this and worked around the threats laid out by Sun during their failed negotiations. Without the patents, Oracle has nothing. It remains to be seen if they have anything even with the patents.