There are x86 images available for the Android emulator, which will run as fast as your host machine will allow.
No. So remind me again what your point is ?
The Android emulator allows you to run applications that were compiled for ARM because it translates the ARM instructions to x86. This is really CPU intensive and can eat a lot of memory as well.
Technologies like Intel HAXM[0] speed this up, which is how the x86 Android images manage to be so much faster than the regular ARM images.
[0]: http://software.intel.com/en-us/articles/intel-hardware-acce...
XCode compiles your source code to match your computer, not your phone, when you run the simulator. With Eclipse and ADT you build for an actual device, and then emulates the device running your app. That's why there's a speed difference.
However, when building for connected devices - both XCode and Eclipse+ADT compiles and runs at the same speed IMO.
The problem with the XCode approach is that some implementations can't be simulated (I remember trying to play a video from YouTube, embedded) - and needs an actual device to work. This hasn't happend with the Android emulator for me, because it actually behaves like a device.
Agreed, the Android emulator sucks and I don't use it. One of its many flaws is that it doesn't support multicast, which is pretty much a requirement for doing device discovery in a remote control app.
I mean, they're tools developed for your job, learn to use them!
It would be like coding using a plain text editor.. you can do it, but it's not what you're supposed to do.
The reason everyone tests on hardware is because the emulator is %@$#ing slow. i7 @ 4.2GHz, 12 GB of RAM... the emulator still takes MINUTES to start and runs unusably slow.
The iOS Simulator on the MBP work gave me (mid-2010) runs at basically native speed.
I do some development with Cordova. During development I either test on my Android phone or an iOS simulator. Those are the only realistic options.