I'm not saying the market is still dead, but for a company like Borland, 10 years ago there was nothing they could have done to recover from Eclipse taking over the market. Even then, IntelliJ was a relative niche product (compared to the vast ubiquity of Eclipse), and JetBrains did diversify their product portfolio to both more aspects of the development lifecycle and to more specialized needs in IDEs. Anyway, my point was that Eclipse was a game-changer that triggered great change in Borland.
I regard Eclipse as a tool of the Devil. I'll be taking up Android again soon. Every time I try I find Eclipse giving me the goatse but now I'm going to use TextWrangler and Ant.
> I'll be taking up Android again soon. Every time I try I find Eclipse [...]
Is there a particular reason to choose Eclipse instead of Android Studio? Google is pushing its weight on the latter with their Eclipse+ADT combo being essentially on life support (and for good reason since Android Studio provides a vastly better experience).
Moreover, the next version of Android Studio will include C/C++ support based on JetBrains' CLion that will cover development with the NDK.
I didn't know about Android Studio, I'll give it a try.
I actually like IDEs quite a lot, what I don't like are IDEs like netbeans, eclipse, visual studio or xcode.
I loved codewarrior absolutely to death, I was heavily into thinkc, the first development tool I ever bought with my own money was lightspeedc which fit on a floppy.
Metrowerks Codewarrior has fond memories for me too (although I have never had a problem with Eclipse aside from bloated J2EE bundles like WSAD etc. It's easy to set it up to be quick and unobstrusive I've found).
Well you're lucky that Eclipse has essentially been deprecated as an Android IDE.
Also Ant? Gradle and Maven are significantly more versatile and better supported for Android development (with Gradle being a first-class citizen now) and I honestly don't advise you to torture yourself with Ant.
