I can understand the Android tries to be one operating system on multiple mobile devices (and their associated chips and CPUs) using java as an intermediate compatibility layer. However, as many people found out wish java, javascript ecmascript, python, and other interpreted languages, they are slow, too slow for cpu intensive applications like 3D apps (including games), apps needing lots of calculations (lots in this group like software based movie players and other things). I think in order for android to succeed it needs to basically go the pedal to the metal route and simply offer different SDK for different mobile devices that use different cpu chips. This way people can program in C or C++ or even assembly language to get the maximum out of the phone. admit it, most java apps on mobile phone are too damn slow, and given that the cpu technology in mobile phones are usually many times slower than desktop versions (in order to save costs and power), this is a very serious problem. another way is to just get android and the OHA to simply choose what chips they support (the faster the chip the better) and develop an OS around it. You don't find any java applications or games in the marketplace that people buy for their desktop simply because they are sluggish compared if you program in C or C++ or even assembly. This is partly why flash succeeded whereas java applets failed, because flash is fine tuned to run at full speed of the chip underneath, and there are multiple versions of flash for multiple OS and chips. I won't go into flash apps being compiled scripts (yes they are compiled, but faster than java applets, but you still don't buy flash apps in stores, only c and c++, or assembly apps), but the main point is that when you go closer to the metal, and offer direct access to the hardware, the better apps and chance for success there is for it. So maybe google can wake up and offer choices. Java based sdk for casual stuff, and C or C++ based sdk for people who want access to the hardware without going through an intermediate layer like java. The Android OS should not be java based, but should be in assembly or C. If it is java based, it may doom like most people using mobile phones these days don't buy java based mobile apps. I have nothing against java, just interpreted stuff that are slow, even if it is "compiled at runtime". I only wish for options for developers to get to the metal directly. Because nothing compares to having access to the chips directly and not through interpretation.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
