This is correct but kind of just shifts the question to "Why doesn't Google do the same for Android?", particularly now that the Honeycomb SDK is out because the Android SDK emulator running Honeycomb is so slow as to be completely unusable even on my quad-core desktop system.
Go native for the dev "emulator" is what I meant, just like Apple does for the iOS SDK.
All of the tools the Android SDK uses to build APKs (even NDK ones) support x86 as a target and Android itself will run on x86. There are certainly some apps that require ARM specific (eg. NEON) instruction sets but those are in the vast minority compared to the whole of the Android App ecosystem and Honeycomb running on an emulated ARM isn't really a solution for even those folks, the emulator is basically useless for everyone now.
Comments
This is correct but kind of just shifts the question to "Why doesn't Google do the same for Android?", particularly now that the Honeycomb SDK is out because the Android SDK emulator running Honeycomb is so slow as to be completely unusable even on my quad-core desktop system.
do what same for Android? go native? haven't tried honeycomb but if it's that slow I say post it as an issue to android dev
Go native for the dev "emulator" is what I meant, just like Apple does for the iOS SDK.
All of the tools the Android SDK uses to build APKs (even NDK ones) support x86 as a target and Android itself will run on x86. There are certainly some apps that require ARM specific (eg. NEON) instruction sets but those are in the vast minority compared to the whole of the Android App ecosystem and Honeycomb running on an emulated ARM isn't really a solution for even those folks, the emulator is basically useless for everyone now.
yes , same here . I cant even explored honeycomb as its emulator is too slo , that's why i prefer runing code direct to device . Its saves time.
adb has lots of problem