On Wed, Apr 1, 2009 at 1:10 AM, Jon Colverson <[email protected]> wrote: > > On Mar 31, 8:42 pm, Stoyan Damov <[email protected]> wrote: >> Aha, maybe I wasn't clear enough. I very well understand that Android >> runs Dalvik, and not Java bytecode, and from what I read on the net, >> this was done to avoid some licensing issues/arguments with Sun. > > I think the main reason why Dalvik was created was to provide a VM > with low-memory requirements, which enables Android to have many VMs > running simultaneously, which enables the security model, which > enables the open platform and Market.
... which disables good games (at least for now), which might make many users not want to buy an Android phone, which accounts to mediocre sales, which makes devs go away from Android... > >> Here I'll put my question as bluntly as possible: >> >> If Google were not forced by Sun because of WHATEVER to NOT run java >> bytecode on the Android, would it be WAY WAY faster for games, apps, >> and the Android stack on top of Linux, which is also a Dalvik >> bytecode, because of the java hardware acceleration? > > IMHO the Android platform, browser and the vast majority of apps > perform very well at the moment. TRUE. I don't deny this. > For apps and games that need bare- > metal performance we'll have the NDK in a matter of months, so I don't > think Android's performance is going to be a problem. I guess by NDK you mean Native Development Kit? (it's the 1st time I see this abbreviation). What's your source that we'll have the NDK in a matter of months, and how many months are these? Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
