Developers Interest

[msandiej]

HAHAHAH...I freakin love you wyrm.

[DzNuts]

to make it simple..
At the moment Android simply SUX. Google is doing the EXACT SAME THING that motorola did with the EZX platform. There is no way to write native Linux applications, they want you to write JAVA only, and run it on a VM, closing the real operating system from the user.
I cannot support a platform that starts like this.

wyrm, like I said the lack of native coding sucks and its a let down for developers. IMHO, I think it is alot to say they are doing the EXACT SAME THING as motorola with ezx, as in there's no difference between the two, when it isn't that simple. I don't know how far you've looked into it, but their api is far more comprehensive than all the j2me specs for motorola handsets available right now and gives much more access to the os than in ezx and it wouldn't be fair to say they are the same, especially with things like xmpp and ftp support available. the only aspect of it that is the similar to what motorola is doing is the fact that the coding isn't native and wrapped in an api consisting of java and xml, at least right now. Of course if I designed a platform I would want to offer a native api and sdk, as I'm sure you would. I mean once openmoko and qtopia get off the ground for ming or any ming-like device, I won't give much attention at all to google's os. but at least it's nice to have while truly open os's are getting off the ground.

UPDATE:
I'm not even some type of serious google supporter, I just think credit should be given where it is due.
however, I guess google addressed the many let down developers publicly, already. read about it here:
http://www.techworld.com/mobility/ne...54&pagtype=all

[wyrm]

@DzNuts
You are right.

They are far more open than Motorola.. They are pushing the kernel support for their Qualcomm based hardware into Mainline Linux, this, by itself is MUCH more than what motorola did...

It is just that i got really frustrated about "early look" code that they released.. I was expecting to get Android running on EZX in some hours, i even reserved some time to it.. All the "openess" announced made me think that it would be really.. well.. Open.

[mack]

Hey wirm, don't fuss. It sucks now but so did EZX until we fixed it a bit. We'll do the same with Android. My Android already has a reasonable environment and native binaries, and I straced the entire boot process and everything that currently runs there. From here, its just a matter of will.

[swifty]

Hey wirm, don't fuss. It sucks now but so did EZX until we fixed it a bit. We'll do the same with Android. My Android already has a reasonable environment and native binaries, and I straced the entire boot process and everything that currently runs there. From here, its just a matter of will.

nice to see you back, mack
please, if you have something for our EZX mobiles,
you know what to do with it.

[DzNuts]

@wyrm
Thanks, glad that you at least see my point. I totally understand you frustration and i think google was aware of how much of a fuss this would cause for developers which is why I think they made those statements in the article to cover themselves.

I mean they still maintain on their information page that they only allow java programming simply, but from that article it seems that some devices will support native coding in the future, so maybe this whole thing is so they can market this os to both mainstream users and developers while it is still technically "open". but, in the meantime my excitement is because I've had so many issues with ezx and still have a few and frankly am looking to either buy a phone with a reliable platform running on it, or put a reliable platform on my MING. I've even been considering windows touchscreen phones. so I'm mostly excited that we will soon have a possible alternative to our ezx, that's alot more stable and more open which will make waiting for os's with native coding that are fully functional alot easier.

@mack
I am not having as easy as a time working with android as I expected. right now I'm just testing the flexibility of it's whole application architecture by making small changes to the helllo world and skeleton app activities and already the apps have become unrunnable on the emulator. on top of that, one of my apps didn't work at all on the first release then worked after upgrading to the newest eclipse plug-in. It seems like they have a ways to go in developing their sdk.

UPDATE: there's a huge hole in either the documentation or the eclipse sdk, that after a random number of times the emulator doesn't run the apps in eclipse right, so from that point on u have to apparently run the emulator outside eclipse before running your apps and reuse that same instance of the emulator, which is why upgrading the plugin fixed it temporarily.

[mack]

@swifty
nice to be back
It has been a while since I did anything on the ezx but if I do anything I'll surely post it. In the meantime, I'm just messing with Android a bit. It shows potential.

@DzNuts
I haven't even tried their eclipse plugin or the java sdk. I'm more into low level hacking so I just looked around a bit and started building my own native stuff.