Android Studio vs Eclipse with ADT (2015) [closed]

Solution 1:

IMO everything you can do with Android Studio (gradle, maven, etc) you can do it with Eclipse faster and easier and i mean "faster, easier" because in Eclipse if any problems arises like "error XX" you do a quick search on yahoo/google/whatever and thousands of results appears of guys who had the same problem and how to fix it.

I've been programming with Eclipse for C/C++ and Java over 8 years already switching to IntelliJ for me is a total waste of time with translates in a huge loss of money, all my clients wants their apps for yesterday and i can't have the luxury of "playing" and wasting time tweaking a really different IDE while i have bills to pay. So in my case i will 100% stay with Eclipse.

Solution 2:

• Indexing. Causes AStudio to load up in a matter of years. Afterwards, same a Eclipse. +E

• Language support. +A

• Perspectives. One has to actually start fumbling for the different
  windows in AStudio once they need to switch between design / debug / code. This hassle was completely taken care of by the use of
  Perspectives. +E

• Debugger. Incredibly slow to launch in AStudio. Even Running an app
  takes ages to complete in AStudio. And on the rare occasions it
  doesn't, one ends up with all sorts of exceptions in his app under
  development or plainly app won't install any longer. +E

• Support. StackOverflow is the main resource in both cases. Just that with Eclipse there is not much need for it. +E

• UI: AStudio is just eye cancer. Eclipse is such a breeze. +E

• Building: gradle > ant; but Eclipse also offers mvn. Also, this is
  the main reason of slow run/debug -ing in AStudio and there is no way around it. You just have to swallow the pill and wait 15-20 seconds
  every time you change a line of code. +E

• Auto-save: just makes me think Google felt I was retarded and this
  feature would save my life. +E

Final score:

A : E

1 : 7

Which begs the question of why in the world did they switch to AStudio. That being said, we naturally have no say in this, we just blindly follow the Man.

Solution 3:

First, Android Studio is created and maintained by Google toolkit development team. That means that seemingly every latest update of Android Development will be pushed to AS at the first time. Second, AS is an integration of different Android Development Tools, including ADT, IntelliJ, Gradle, Maven, Ant...You know, ADT could be pluggin in many different open-source development tools, like Eclipse, IntelliJ, NetBeans...When you migrate projects from one to another, some problems could be caused because they have different programming rules and formats which pains not only developers but also Google's and Android's. That is a question. So Android Studio may be a solution for this.