Eclipse is a constant source of small annoyances for me, none of which by itself is a huge deal but when taken together color my view of the editor negatively.
Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately).
I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the Pro version of IDEA that I would seemingly need to get any Perforce integration working is priced at a point ($499 and up) where I'm not sure I could make a justification for the purchase. Eclipse kinda sucks, but it also mostly works and the perforce integration on it is free (and also quite good, I have no idea if IDEA's is any good).
I could, of course, just eschew IDE/VCS integration, but editor integration is, in my experience, kind of a big deal with Perforce because of the rather old-school model it uses of checkouts. It becomes really annoying to merge code in if you don't preemptively check things out before you change them, and having the IDE manage this by just checking things out when you first start editing them is a huge win. Pseudo-ironically, if the VCS I used were any of the ones Android Studio/IDEA gives you for free having support for it in the IDE would be less of a big deal for me, I'd just do all the VCS stuff at the command line.
I work at a company that mandates Perforce for political reasons and getting budget for a $500 purchase when I can't reasonably articulate the benefits over the free thing we've been using all this time would be an uphill battle that I'm honestly not sure is worth it, because while I find Eclipse annoying I don't have enough experience with IDEA to know that it is not annoying in a different set of ways.
I suppose I will try the 30 day demo of IDEA and see if it is worth fighting for, but probably not until Android Studio is more baked because I've played around with it enough to know that the 0.1 designation is warranted at this time.
I can't even begin to calculate the amount of time I wasted on Eclipse. I hated it. I tried to use eclim, which kinda work, but started crashing vim (infrequently) which is worse than not having anything. At least once every two weeks (for three years) I would get so fed up with how slow it is that I'd spend an hour or two trying to fix it.
It's hours and days wasted, and that's before I consider any difference in productivity while actually using each IDE. If any of this sounds familiar, do spend a couple of weeks in the free version of IDEA. It was night-and-day for me. The worst part will be your muscle memory (e.g. stepping through the debugger).
Unfortunately, switching to Android Studio presents a different set of issues, like lack of Perforce integration (using Perforce is out of my control here, unfortunately).
I'd assume some sort of hybrid Android Studio/IDEA setup is possible, but even still the Pro version of IDEA that I would seemingly need to get any Perforce integration working is priced at a point ($499 and up) where I'm not sure I could make a justification for the purchase. Eclipse kinda sucks, but it also mostly works and the perforce integration on it is free (and also quite good, I have no idea if IDEA's is any good).
I could, of course, just eschew IDE/VCS integration, but editor integration is, in my experience, kind of a big deal with Perforce because of the rather old-school model it uses of checkouts. It becomes really annoying to merge code in if you don't preemptively check things out before you change them, and having the IDE manage this by just checking things out when you first start editing them is a huge win. Pseudo-ironically, if the VCS I used were any of the ones Android Studio/IDEA gives you for free having support for it in the IDE would be less of a big deal for me, I'd just do all the VCS stuff at the command line.