writes "An efficient IDE with good debugging tools is essential for a happy coder. Why is it then, that after 2 and a half years the Android SDK is still so bad when compared to environments for other devices? It's not like Google are lacking in-house talent, but despite acknowledging the terrible emulator performance, (including lack of OpenGL support) and clunky GUI building tools, nothing seems to be happening to address the issues. The emulator's performance is blamed on it accurately emulating a device, unlike the iPhone/iPad simulators. However, I believe most developers would like to build against a usable emulator, even if it's not 100% accurate. Let's face it, devs on other platforms devs have had no problems with this model. An emulator/debugging tool that struggles to reach 1/2 the speed of an old G1, while running on an i7 950 with 12GB RAM, is really not cutting it. The fact the emulator only uses 1 core of the CPU doesn't help, obviously.
If Microsoft had produced something like this for people to develop for WP7, there would be universal derision, so why are Google getting a free ride with this?
It would be interesting to hear the views of other Android developers, and how they fare with the current SDK."Link to Original Source