So only neb (see what I did there?) will read this, luckily he's the only one who will care.
I don't understand why Oracle would want to sue Google. Yes, JavaME was the only way that Sun made money (which means it's the only way Oracle will make money from Java) but they're shooting themselves in the foot by hurting Java's only Champion.
No one else helps people use Java. Apache was the champion before. They brought us Tomcat and thousands of other amazing libraries that everyone should be using. Spring sorta still is, but honestly I'm tired of thinking Spring is the new awesome. Everything they do now is soak up smart shit someone else thought of.
Google helps developers. With Google Web Toolkit (GWT), Google App Engine (GAE) and Android, they're the ones pushing new and exciting things and making Java EASILY ACCESSIBLE to developers. Want to make a webpage but don't know shit about javascript, use GWT. Want to create a website but you don't really want to pay for hosting because hosting java sites is way more expensive than their .NET equivalent (and you don't want to do php?) then you have GAE.
Want to develop a mobile app with basically NO BARRIER TO ENTRY and a very large customer base? That's Android for you. It's free, if you want to list it on the market, it's $25 (not sure if that's a yearly fee or not). You don't even have to pay that, and just distribute it on your own website (maybe the website you created in GAE). Seriously, Google has made it easy for Java Developers to get their stuff out there. They're the only ones who've taken an interest in Java.
Now Oracle, the company that has forever pushed out terrible shit, is getting pissy. Yes, their databases are good (although lest be honest, we're hitting the limits of relational databases). EVERYTHING ELSE ORACLE DOES IS CRAP. There's no reason to use it.
Remember 5 years ago when Ajax was the buzzword and everyone had to Ajaxify their websites to do cool things? Oracle took that concept and was like "we could use new technologies, but we don't want to. We'll create a hidden IFRAME, do a form post...then read the response, and update elements on the main page. To be fair, this was the only way to do it before people mistakenly found out about Ajax (the XmlHttpRequest javascript thingy). So there's no real issue. The problem is they rebranded all their old stuff by slapping the new buzzword on it.
This was a very annoying problem in their initial JSF controls (which I think they later submitted to Apache) because it brok the JSF lifecycle. But that's more of a JSF sucking than their own fault...maybe.
I've read quotes from the "Father of Java" about how Android fragmentation is the biggest problem in the world. "Seeeeee?!?! I told you Android will fail, there's too many devices and the update cycle is too fast and we can't keep up." I remember the Sprint CEO saying that he didn't want to get into the Android game because it was too unstable. What eventually happened? They released the EVO, and I think they had their first profitable quarter in forever. I'd really have to go back and look at the numbers to see that the EVO was on sale during that quarter, but for whatever reason I think that's what happened.
tldr version; Oracle, don't kill your best friend in the Java world, which unfortunately for privacy, is Google.
