Posted by: gowrisivaprasad | November 13, 2007

Google Android and NetBeans

Android Logo Netbeans Logo

Jonathan Schwartz, CEO of Sun Microsystems, in this blog entry seems to indicate that NetBeans is a supported IDE for Android. This is what he specifically says:

blockquotes.gifI’d also like Sun to be the first platform software company to commit to a complete developer environment around the platform, as we throw Sun’s NetBeans developer platform for mobile devices behind the effort. We’ve obviously done a ton of work to support developers on all Java based platforms, and were pleased to add Google’s Android to the list.blockquotes.gif

But in the Android SDK announcement and documentation, Eclipse is the only supported IDE. There is no mention of NetBeans.

Where does this place what Jonathan said? Was he saying that Sun will build a NetBeans plugin for Andriod and release it on its own, or is he speculating that Google might add NetBeans support later? Maybe he was just hoping for some hype by association with a hot news (certainly not his style though)!

Given all the documentation that Google has provided for Android SDK, it should not be hard to build a NetBeans plugin for Android. But it is kind of a blow to Sun that Google chose to do its own Java VM implementation as well not support NetBeans as a supported IDE. Maybe Google didn’t like CDDL license.

Usually Jonathan’s blog gets mostly supportive and appreciative comments. But they just took it out on him for this entry.

Update:  There seems to be a good amount of interest in using NetBeans for Android development. This is a good opportunity for the NetBeans community to step and fill the need.

Responses

what I don’t understand is why Google is trying to create some funky Java derivative. And trying to abscond with a Linux kernel and ship it under an apache license. Seems like folks are taking them to task for trying to pull a fast one, too. Plus, they don’t have a phone… just hype.

Perry: My guess is Google wanted control or didn’t want to maintain compatibility with TCK. They probably predicted that they would want to diverge from the standard in the future and to go their own way from the start would be the easiest for them.

It is unfair that they want the Java syntax that everyone is familiar with (meaning, that much easier developer adoption) but don’t want the standard Java VM.

I am surprised Sun is not crying fowl, given all the prior noise they have created around companies forking Java.

Leave a response

Your response:

Categories