It's not a performance thing. It's a productivity thing. Eclipse is not particularly intuitive for an IDE (and if you're a java developer who uses it all the t

It's not a performance thing. It's a productivity thing. Eclipse is not particularly intuitive for an IDE (and if you're a java developer who uses it all the time, you have no clue if it is as you're past the point where you're learning it). Eclipse is very testy on some platforms to get working Eclipse really confuses the issue when there are some compile errors in your android code. Eclipse is a fullscale ecosystem for some problem you are not solving (largely enterprise java development). 90% of the tool has nothing to do with android. Most if not all of the "Android Plugin" is calls to standalone EXE's you can use without eclipse, and which make gobs more sense when eclipse isn't doing the calls for you. I honestly made a pretty pure run using Android via Eclipse, then read 1 article of "Android Without Eclipse" and was able to Compile repeatedly, deploy and debug the apps I was working with easily once I jettisoned it.