Comments on: Google's Android parts ways with Java industry group

Heads up, programmers: Google opted to create its own Java standards and technology for its Android mobile phone, not piggyback on the existing Java Community Process.

[alflanagan]

Well, duh

The way the Java Community Process is set up, if Google went through that they'd release in, oh, 2011 or so.

First Eclipse finally gets client apps to work by writing a _whole new graphics library_, now Google's got a whole new mobile implementation. Eventually, despite Sun's best efforts, Java is going to actually work.

[tenbosch]

Deja Vu!!

I'm I the only one that remembers when Microsoft did this? Sure, it was faster, but really proprietary. Google is trying to create a new standard by hoping for mass deployment of gphone apps. I think the last thing any developer needs is another fork in Java, or any programming language for that matter. Why couldn't they work with the existing Java community to create a modified mobile standard. It's a shame...

[fletchb]

java

Because its bloated and slow. JM seriously slows down your machine and sucks up resources. If google can develop a decent working version I say more power to them.

[ramonck]

New features and platform requires new APIs, duh!

You want plain old JME with a Linux robust platform.. ofcourse it's always going to be parted away... welcome to linux on mobiles.. welcome to android.

[nonstopgenius]

I remember when Microsoft did the same thing, Sun took them to court, Google is the next microsoft and they seem to be getting away with some of things microsoft could not.