| >So easy for anyone that has suffered throught Android development. The pain of Windows phone development was significantly worse especially when you consider they kept on changing it every year because of their inferior development environment and tooling. >Starting with Eclipse, then rebooting the whole development environment just because some management guys happened to be InteliJ users. Google switched IDE's. Microsoft changed their development environment and tooling each time they decided to osbourne their still born OS. >NDK is treated as a 20% project, done by an handfull of engineers. Well, at least they stuck with it instead of chucking it to the curb each year and starting over. >Devs were left in the cold when the migration away from Eclipse was decided. It was only due to the coincidence of Clion being developed, that Studio eventually got C++ support. Isn't being left in the cold an annual event for Windows phone developers? >The decision to use Gradle has made "how to optimize builds" a recorrent topic in any major Android conference. This is in contrast to the Windows phone .build conference where there were no sessions because no one was building Windows phone apps. >Google teams like Android development build tools so much that they rather use blaze, throwing yet another build tool into the mix. Isn't choice good. >There isn't a single release of Android Studio or the Support Library, that isn't followed by bug related complaints on online forums, despite being several weeks, months, in testing phase. Because XCode and Visual Studio are bug free when new versions are released, right? Oh wait. >Their initial emulator implementations was so lousy, that it required the public shame of Genymotion and Microsoft doing a better job for Google actually improving theirs. Google has to support 3 platforms unlike Microsoft who couldn't even support 1. |
Vastly superior to Android Studio.
> Google switched IDE's. Microsoft changed their development environment and tooling each time they decided to osbourne their still born OS.
Google replaces Android Studio plugins at each major release.
Profilers, Gradle configurations, IDE plugins
> Well, at least they stuck with it instead of chucking it to the curb each year and starting over.
It already started over 4 times, with incompatible build systems.
> Isn't being left in the cold an annual event for Windows phone developers?
Not as much as at Google IO. Oh sorry, maybe you are right we don't feel the cold as we are taking care of our sun burns.
> This is in contrast to the Windows phone .build conference where there were no sessions because no one was building Windows phone apps.
There is no such thing as Windows Phone specific conference, there is only BUILD conference, Connect conference and Windows Developer days.
> Isn't choice good.
Not when it increases development costs.
> Because XCode and Visual Studio are bug free when new versions are released, right? Oh wait.
Android Studio wins in bug counts.
> Google has to support 3 platforms unlike Microsoft who couldn't even support 1.
Strangely, you cleverly forgot to mention Genymotion.
As for Microsoft their Android Emulator still runs better than Google's on Windows.
Maybe Google needs to do less inverted balanced tree whiteboard interview exercises and more OS related stuff.