it seems really weird to me you find netbeans complicated. There's a reason java developers use bloated IDE's for anything more than quick edits. Spend a week in Netbeans and I bet you a lap dance you keep using it.
I'll second that. As a seasoned eclipse user I had another look at Netbeans recently. It seemed pretty much the same for me, and offered no compelling reason to switch. Until I poked around the profiler.
Well, let me say there's no going back for me. The Netbeans profiler gives me confidence from knowing exactly what my application is doing, and exactly what that third-party library is costing me. The coverage, allocation stack traces, and jvm heap monitoring are fantastic. Seriously. Take a look: http://www.netbeans.org/kb/60/java/profiler-intro.html
So yeah, I'll take a slice of that action and throw a pole dance in on that lap dance you bet. And it didn't even take me a week before I realised.
If you jumped from Eclipse to NetBeans, there wasn't any pain from the different plugin offerings? I don't enjoy installing two IDEs for the same language, but that's what I end up doing, unhappily.
No pain at all. I don't rely heavily on plugins though. The important bases were covered: refactoring, vcs integration, and the usual javadoc/outlining.
Perhaps the only things I missed were getting a method's signature when you hover over it with the mouse, and the live variable value when you hover in debug mode. But these are so minor that I feel if they're not already there and I somehow haven't set them up, they'll be in the next release. But as I said, I get so much more confidence by being able to charge in to my code's runtime and poke around that it's worth it.
