Hacker News Reader

Comment by udp | Hacker News Reader

Those doing Android dev and stuck with Eclipse should also check out nbandroid: http://wiki.netbeans.org/IntroAndroidDevNetBeans

It's such a breath of fresh air having a responsive IDE... now all I need is a responsive phone ;-)

View on HN

Funnily enough, I gave up on Netbeans 6.9 because it was soooo slow to react to input !

It is a really well-thought-out, user friendly IDE (much better usability curve than Eclipse imho), but I couldn't stand the constant scanning it does for some reason or the other, and slows the world down.

Have to check if there are improvements ..

You can turn of "Enable auto-scanning of sources" which makes it loads better.

But netbeans will still have to scan projects from time to time. I've had to keep just a small number active at any time to prevent it from scanning too much and slowing down.

Those two steps do help a lot though.

responsive compared to what trash? Eclipse IDE has better performance on most OSes and the Adt plugin in fact keep sup with the google sdk releases unlike nbandroid plugins...which at times you are waiting 3 months for an update to match the current android sdk.

I can't really argue with you because I'm only speaking from my own experience, but although with nbandroid I might wait 3 months for an update, with Eclipse I would wait 3 months for the code completion popup.

:-)

You might want to edit your eclipse.ini and give it more memory[1] ... It worked like a charm for me on my Mac. The linux boxes I use don't have this problem.

[1] The properties you want to change are: launcher.XXMaxPermSize, XX:MaxPermSize, Xms, and Xmx

Now that you mention it, it wasn't shy about how much memory it wanted to use either, but I'll give it a try next time I need to use Eclipse for something - thanks.

Code completion in Eclipse was a killer for me as well. I switched back to Netbeans for Android development (used it for php and python before) and was very happy. The only reason I switched to Eclipse in the first place was because all of the Android books and tutorials I found used it and it was easier to follow that way.

Haven't used Eclipse for a while, but I'm pretty sure the amount of time you wait for the pop-up is a setting. Set it to zero and it's instantaneous on most modern hardware.

No, this is a full "IDE locked up" kind of delay - and it's not just code completion, the whole thing feels sluggish compared to Netbeans. This is both on my Windows desktop and my MBP, so I guess the only thing left to blame is the size of the codebase I'm working with.

good tip

Reply on news.ycombinator.com