Netbeans vs Eclipse

The last couple of days I have desparately tried to use NetBeans for some of my work instead of Eclipse. Read on for a skimmy comparison (or rather, a list of issues that I found with NetBeans)…
I wanted to use NetBeans for GNU Classpath development. This aims high, but after all, most of my projects in NetBeans are GNU Classpath related. I wanted to use my existing working directory which turned out to be easy: In NetBeans you can have a project directory that is separate from the sources (just like in Eclispe AFAIK). But then the problems started. I list the issues that were hindering my workflow badly:

  • NetBeans lacks support for complex project classpath settings like there is in Eclipse. I can set up a couple of source directories, that is fine, but I can’t define include/exclude patterns, which is necessary for GNU Classpath’s crazy directory structure. My workaround was to hack the project’s ant scripts. This works fine for the compilation, but isn’t perfect, as NetBeans itself still sees the convoluted sources in the completion, search etc.
  • Compilation just isn’t as smooth as in Eclipse. In Eclipse I usually don’t have to worry about that at all. I simply save a file, and it gets compiled automatically (including dependency resolution). In NetBeans I can either compile a single file (F9) or the whole project, both of which seems to be suboptimal: The whole project takes a coffee break of time, and I am already consuming much too much coffee. And compiling a single file without dependency resolution seems to be a little shaky. And then there is the bootclasspath issue, which completely breaks single-file-compilation:
  • For a project like GNU Classpath I need to be able to tweak the bootclasspath so that the compiler doesn’t mix up the the classes from the JDK that NetBeans runs on, and the classes in the project. Again, I can do that for the ant scripts which is fine, but not for the IDE in general, which leads to the strange effect that I get errors all over the place because some CP-internal stuff can’t be found in the JDK’s classes, but when I compile the stuff completely it works.
  • The support for different coding style is, well, more or less non-existant. I can only tweak the indentation and the braces and that pretty much was it. Leaving me with manually doing the coding style thing. This is unacceptable for me, all other IDEs I use (Eclipse and Emacs) do this quite well for me.
  • I just love the useful warnings in Eclipse, for instance for unused imports and such. This simply doesn’t compare with NetBeans.
  • Strange enough, I can’t seem to do a refresh (in Eclipse: F5) of the source tree. So when I do something outside the IDE, I can’t sync that, except by restarting the IDE.
  • Update: NetBeans seems to also implement the very useful navigate-to-class feature (CTRL+SHIFT+T in Eclipse). However, I very much miss the quick-outline (CTRL-O in Eclipse). This is such a massively useful feature that I wouldn’t want to live without.

I desparately tried to use NetBeans, I really want to use it, mostly because I love Swing (and NetBeans with the GTK L&F integrates very well in my desktop, kudos!). But the above issues are hindering me in such drastic ways that I better stick with Eclipse. I see that some of the issues are beeing worked on, others probably not. When I get around to it I probably file some bugreports…


4 Responses to Netbeans vs Eclipse

  1. Dave Gilbert says:

    Hi Roman,

    My experience was similar when I did the JavaTools 30 Day IDE Challenge towards the end of 2006. NetBeans is really polished, but in a few places (the ones you mentioned, mainly, but I’d add JUnit integration as well) Eclipse is more flexible / usable. It looks like they’re working hard on NetBeans, so I’ll look at it again later in the year, but for now I’m still using Eclipse.

  2. Tom Tromey says:

    I tried using netbeans on classpath a couple years ago. I wrote a little blog entry about it, but I can’t find it right now.

    Anyway, it didn’t really work out.

    NetBeans has some really nice things. Matisse — which I’ve seen demoed but have not used — looks very, very good.

    However, AIUI NetBeans just runs javac, perhaps via ant. This can never compare with having a built-in, fine-grained, incremental compiler the way that Eclipse does. IMNSHO.

  3. Mario says:

    I think they are different tools, in the end. I found Eclipse great as an “editor”, a good platform for doing thin clients, and great to work on classpath :). It simply does not compete with Netbeans as a tool in: Swing development (matisse); J2EE, sjas and glassfish are so integrated you can even setup secure webservices and control the databases from NB, JBoss also works really fine; Web development (you can design the web forms using a Matisse like tool); J2ME, well, the mobile suite is a productivity dog. Eclipse forces you to do things in another way, I could say, it forces you to know what’s going on and does not do the dirty job for you, but pays back with a great flexibility NetBeans lacks.

  4. spajxypyw says:

    I swear, can see fine. That withme before i milf redhead sat down on the breeze.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: