The shit finally hits the fan....(James Gosling on Oracle vs Google)
nighthacks.com
nighthacks.com
My thinking is this: Even though the company would only use it for "defensive purposes" (which I believe), you never know who owns the company tomorrow. And you are not going to work there tomorrow either, so you might be the one being sued.
Instead, I would try to get permission to blog about it, so it is available for everyone -- including my future self.
I recommend everyone else do the same!
(Throw-away account - I'm not sure future employers want this)
Easy answer: "of course there's nothing patentable here--it's software!"
1. How difficult will it be for Google to 're do" Android and base it on another language say Objective C/UNIX like iOS? 2. Do you guys think this will affect Symbian? 3. What other OS's will this affect? 4. Is MYSQL next?
As to 2 and 3, this probably won't affect anybody else. Symbian (and everybody else) use an officially licensed JVM from Sun(now Oracle) and as such should be safe. The reason Google is in trouble is that the wrote their own VM rather than licensing the VM from Oracle.
As to 4. Well that's anyone's guess.
If I'm running MySQL on some servers, and it works great, it's not going to suddenly explode, or stop working.
Wouldn't it be great if Android would be based on a better language than Java?
The Dalvik VM is the only thing these threats are about.
> Wouldn't it be great if Android would be based on a better language than Java?
You can already write Android apps in Python, Lua, Scheme, Ruby, Scala, Clojure, Fantom, Mirah, and Javascript. This is precisely due to the fact that Dalvik is closely related to the JVM.
I have written an app in JavaScript going the HTML5 route, but it required some Java glue code. The JavaScript engine is V8 (at least on Froyo), so it is fast.
But Oracle doesn't want a patent war with IBM and Microsoft just now. Microsoft could simply ban Oracle from running on windows, or ban any windows machine from connecting to a site using Oracle (a bit of Apple style licensing text is easy to insert)
And you don't want a patent fight with IBM - they probably have a patent on using oxygen for breathing!
Maybe they could use Go for this purpose. (This would be a nice opportunity for Go.)
Go is not ready for something like this, NO CHANGE. Go as a Language and as a Platform is not ready.
4-Yes, MySQL competes with Oracle, so... they will let it die slowly. They want db systems to be expensive, not cheap.
— Gosling, comment on linked article.
"So say goodbye to the NAACP award […] But I'll just take the "I Got A Lot Of Cheese" award"
— Kanye West, "Everything I Am"
The problem is a middle-term one: open-source will shy away from it (and the Apache/JBoss libraries are A Big Reason to use Java), academia will begin to stop teaching it (for all the "it doesn't matter what language you use" arguments, there are many mediocre programmers who can only handle the one thing they are taught), and new company projects will try and avoid the license fees and choose unencumbered languages. That sort of thing won't hurt Oracle now, but it will in five to ten years.
Heck, if Microsoft ever saw the woods from the trees and freed C#, bought the Mono devs and pushed the .NET ecosystem to other platforms, creating a sea of programmers that use their language alone, Oracle could feel the results of this in less than three years.
Microsoft's conversion to open source is going to have to be really really convincing after yesterday's precedent.
There are 3 things Java the Langauge JVM and the JDK (not sure if this is the write name i just meen the libs around it)
The language itself has shown that it probably isn't going to get past version 7, and even getting that through was by cutting a whole lot of features (lol closures lol?). However, that would just mean Java faded into insignificance when a new leader emerged. I think this may well have fallen to Scala given time. Oracle is unnecessarily hastening Java's demise, and from my limited understanding of the reporting, might be taking the JVM with it. That's a really bad thing for software development in general.
11. Its daddy is in a pinch. Sun's business model is being undermined on two
fronts. Cheap Intel processors, of the same type used in desktop machines, are
now more than fast enough for servers. And FreeBSD seems to be at least as good
an OS for servers as Solaris. Sun's advertising implies that you need Sun
servers for industrial strength applications. If this were true, Yahoo would be
first in line to buy Suns; but when I worked there, the servers were all Intel
boxes running FreeBSD. This bodes ill for Sun's future. If Sun runs into
trouble, they could drag Java down with them.
Prescient. I hadn't read that essay before.> If Sun runs into trouble, they could drag Java down with them.
[ 'trouble' could of course include 'nonexistence' or 'sleeps with the enemy' ]
* Companies (more specially: Enterprises) must trust you or they won't use your technology
* Library makers must have trust in you or they will not continue building libraries for your platform
Only two examples, but I think they highlight the point: Nobody will invest in a technology/platform/programming language they do not trust. And starting patent lawsuits against companies that use your platform is a great way to loose trust.
While Android/Davik technically is not a Java VM that is not what most people will see. Most people will see "Oracle starts lawsuits against companies using Java"All things being equal, Oracle suing somebody and doing it in part because of "java" does have to make you take notice if you do anything with it. It's not like there is some open standard for Java and 10 different yet fairly equal implementations to choose from like it is with a C compiler. For serious java work, there still are maybe 3 implementations (Sun's, IBM's and maybe OpenJDK?) and they share some common components and ancestry.
Time will tell though, we'll see what happens. The java haters will continue to hate it, the java lovers will continue to love it and then those in the middle will have a raised eye brow and sort of pay attention.
As many other said before, the fact that OpenJDK is GPL licensed doesn't mean anything for Dalvik.
IMHO OpenSolaris won't represent much more than NetBSD pretty soon.
I don't use it, but it does have some things to offer.
So, if he saw their eyes sparkle that means that he is saying that he had an inkling that they were going to use that patent, and then he says "I hope to avoid getting dragged into the fray".
Great guy, not only does he sell a cocked gun to a company that is well known for using guns, on top of that he hopes that he's not even going to have to testify.
So he must have been in on the negotiations only because of his name being on those patents, or his unique understanding of those patents or something to that effect.
I find it strange to see him talking to the Oracle lawyers explaining the patent situations in a 'we're selling you this asset with which you can attack google' mode, and to come out now and act all surprised and 'I hope I don't get dragged in to it' mode.
He should probably expect to get dragged in to it, most likely by Googles council as a witness for the defense.
If he presented it to Oracle in a way that 'made their lawyers eyes sparkle' that sounds like he presented it in a very favorable light (for Oracle and Sun) during those meetings, if he's going to be dragged in to it he will have to repeat his stance on why this is something that Oracle can do in court or he'll risk being sued by Oracle for misrepresentation during the meetings with Oracle if he comes down on the defense side with his point of view.
I really wouldn't want to be in his shoes, this could get very nasty. And it could damage the Java brand considerably.
Also, it's not clear whether any special presentation was needed to make the lawyers' eyes sparkle, other the mere possibility of extracting licensing fees from Google.
It isn't clear whether the integration meetings Gosling referred to occurred before, or after, the Sun-Oracle deal was made. Whatever the case, I expect Gosling was asked to attend those meetings as a Sun employee, and that he explained the patent situation in an open and honest manner.
What do you think Gosling should have done? Deceived Oracle during the acquisition talks because he didn't like what they were planning to do?
dragged in to it he will have to repeat his stance on why this is something that Oracle can do in court
Where has Gosling said he won't repeat the same stance?
http://tech.fortune.cnn.com/2010/08/10/vint-cerf-comments-on...
The art of the understatement.
Oracle bought Sun and everyone was concerned because Oracle is very evil.
So anyway my understanding is probably Google has some agreement or plan at hand for this situation. Ideas welcome.
The server JVM is very mature; millions of dollars have been poured into making it work great in long-running, high-memory conditions where it has a lot of time to optimize its JIT. The client JVM (focusing on quick startup and low resource usage) has been pretty much neglected ever since people realized "Java applets on the web" wasn't going to happen.
That's because register IRs are easier to optimize than stack based ones. Have you heard of SSA? the canonical intermediate representation for high performance compilers; yeah, it's register based.
And Dalvik wasn't the first recent VM to be that "different"; heard of Parrot? it's register based.
Also, Google is betting on mobile big. And if you want to play in that space you better have your own platform and not depend on someone else's licenses. I think it only proves that it was the right move: JVM is now owned by assholes and being in court for patent "infringement" with them is still a lot better than betting the company future on the OS based on a platform owned by assholes.
[1]http://discolab.rutgers.edu/classes/cs672-fall00/j2me/Append...
Google isn't infringing on the patents and sure isn't violating the copyright. Oracle knows that a Texas jury won't understand the technical issues and hopes Google will settle to avoid the chance of losing billions over a bogus and ignorant verdict.
The outcome of a jury trial in a case like this is like flipping a coin. There won't be any hackers on the jury or else it'd be a five minute decision out of the jury room for Google.
And they certainly know RIM develops its own since they say so right on their own site: http://www.oracle.com/technetwork/systems/index-139239.html
RIM's support for J2ME includes development of its own Java virtual machine (JVM) 1, which supports the Connected Limited Device Configuration (CLDC) and the Mobile Information Device Profile (MIDP).
The gist of the matter is right there. Since RIM supports J2ME, it means they have paid Sun, now Oracle for a J2ME license. That was one of the things that Google bypassed by writing their own implementation.
See this comment on the other discussion: http://news.ycombinator.com/item?id=1599834
I won't even pretend to understand Sun's ownership of the JVM IP, the licensing agreements it had with JVM implementors, patents etc. But my view from afar is that Google tried to route around all that by using a different VM architecture, but (possibly) exposed its self to a different set of legal vulnerabilities.
Oracle finally filed a patent lawsuit against Google. Not a big surprise. During the integration meetings between Sun and Oracle where we were being grilled about the patent situation between Sun and Google, we could see the Oracle lawyer's eyes sparkle. Filing patent suits was never in Sun's genetic code. Alas....
I hope to avoid getting dragged into the fray: they only picked one of my patents (RE38,104) to sue over.
Ref: http://en.wikipedia.org/wiki/Android_%28operating_system%29#...
I was unable to ascertain whether Dalvik came from Android, Inc. or was created by Google after acquiring Android. My memory says the later.
The Dalvik VM is an end-run around the Sun JVM licensing issue: http://en.wikipedia.org/wiki/Dalvik_virtual_machine
See especially the reference http://www.betaversion.org/~stefano/linotype/news/110/
This raised more than one eyebrowse, and sure did make me raise mine: how did Google manage to get Sun to license off a platform that could very well kill their own?
Turns out, they didn’t: their move was even smarter than Sun’s.
Today Google released the Android code and I took a serious look at its internals... and found the solution for the licensing problem. It’s called Dalvik and it’s the new name of Sun’s worst nightmares.