Shizzle

My little notebook

In praise of Netbeans (and how I learned to hate Eclipse)

Published on August 10, 2009

The dark ages

I use a MacBook for my development and until recently I have done my Java development in Eclipse. It is a very popular IDE and apparently very flexible and can be made to do absolutely everything. Also, all the Google Java products plugins only worked for Eclipse and that was the main reason for me to not switch.

However, it shortcomings became more and more apparent during the time I wrote my dissertation and became more serious about Java development. I noticed the following things about the OS X variant of Eclipse.

  1. It. Is. Slow. It is painful to work with an IDE that locks up every 5 minutes and whenever you open a menu that has so far not been opened. I heard something about the Java-Carbon bindings not being very good and I think performance is better on Windows but this was a real issue for me.
  2. Usability is abysmal. There are millions of message areas that pop up all the time, buttons are tiny and appear and disappear seemingly randomly. I know software development is supposed to be difficult but this is just unbearably hostile to the user.
  3. It is very much a Windows app. It feels a lot like they wrote the app to fit with the windows UI guidelines, realised that there is Mac developers too and just copied the UI button by button. I know us Mac people are demanding when it comes to OS integration but Eclipse is simply not cutting it.

The conversion

One day I was frustrated enough by how rubbish Eclipse was, that I was ready to switch IDE mid-project. I kept saying to myself that I would give Netbeans a spin at the next project but my patience with Eclipse was wearing thin. I have not looked back.

The main issue I was worried about was the project conversion process and I have to tell you it was the most seamless thing I have ever experienced. Absolutely no errors or incompatibilities turned up. I was impressed. It also turned out that Netbeans is much better at managing your classpath automatically, so conversion even resolved a few issues. The only thing I had to redo was the tomcat configuration but that took about 30 mins.

I didn’t know Java development could be bearable on a Mac

After trying Netbeans out for a few days I have the following things about it.

  1. It has a nicer UI. I know this will not get me any cred with the emacs crowd but if an application doesn’t shout “I’M UGLY!” all day long I like using it better than one that does. Call me superficial.
    I also managed to install a dark editor skin which makes Netbeans resemble Textmate a bit more which has also earned some plus points with me.
  2. Usability is way better. Buttons are clear and there are fewer of them. Netbeans also gives you more sane default behaviour so you don’t have to poke around in the settings too often.
  3. Classpath and lib folder management works. When you put something in the lib folder, it will be put on the classpath and copied into WEB-INF/lib. I couldn’t get Eclipse to do that no matter how hard I tried. I had to enable this for every JAR I downloaded.
  4. It’s faster. Not Textmate-fast but fast enough to not annoy me constantly. I like.
  5. Mercurial works out of the box. I didn’t install a plugin, I never activated anything. Netbeans just knew I was using it and started marking files as edited. (I guess this works for other SCMs too.)
Netbeans screenshot with Textmate style dark theme

Netbeans screenshot with Textmate-style dark theme

In retrospect, switching to Netbeans has been a huge boost in terms of productivity for me. I’m wondering why I didn’t try it earlier.

Filed under: Mixed
Tags: , , ,

7 Comments

  1. Ala Al-Shaibani says:

    Guess I’ll be giving it a try as well :P you sold it lol.

  2. Rob says:

    My main complaint about Eclipse is option overload. It’s way too busy. I remember being really frustrated because Eclipse stopped showing the location of the file in my Package Explorer when I brought up files in the Editor. It took me a long time to figure it out. I had accidentally clicked the “link” button on the Package Explorer that links it with the Editor. Little things like that shouldn’t be so easy to screw up.

  3. Jul says:

    Hey

    Could you please send mi your skin!

    I really like netbeens but i didn’t find a dark theme!

    regards

  4. Lenni says:

    The theme is called Dark Pastels. I think it comes prebundled with the Ruby flavour of Netbeans and should be available from the plugin menu.

    Alternatively, you can get it here: http://mediacast.sun.com/share/tor/org-netbeans-modules-ruby-themes.nbm

    You can read on Tor Norbye’s blog about it: http://blogs.sun.com/tor/entry/ruby_screenshot_of_the_week19

  5. Jul says:

    Hey thank you!!
    The theme is really cool!!

  6. droope says:

    Today I tried Eclipse…

    I almost died :P It was a very painful experience.

    I am using netbeans now. I have managed to use a dark color scheme, too :)

    Regards!
    Droope

  7. Conrad Braam says:

    Eclipse was not written for Windows either, since you correctly purport it was not for Mac, it’s probably a GUI port from someplace else. I do find it is hard to use for all of the same reasons. Moreover sometimes you have to click on a button twice, and yet other features only start working for the first time after you re-start Eclipse; such bugs spoil it for n00bs. I would say something nasty now, but it would profit me not, so one nice thing about Eclipse is that it probably gets easier to use after about 3 years of using it.

Leave a Reply

Switch to our mobile site