Slashdot Mirror


NetBeans 4.0 Release

An anonymous reader writes "Various news sources are reporting the 4.0 release of the free Java-based NetBeans IDE. You can read the anouncement, or proceed directly to the downloads. Perhaps the most significant improvement is that the IDE's native build system is the latest version of Apache Ant. I see this as a distinct advantage over its competitor Eclipse (and NetBeans is pure Java). If you create desktop applications in Java, you may wish to read up on the NetBeans 'platform' as well. Enjoy."

5 of 45 comments (clear)

  1. hideous code by sporty · · Score: 2, Informative
    2 points.


    1. prior versions of netbeans auto-genned fugly code for the gui's you laid out.


    2. Many people I know do visual coding by hand, similar to html to some degree.

    --

    -
    ping -f 255.255.255.255 # if only

  2. Pure Java? Ant as an advantage? by chochos · · Score: 2, Informative

    Is this a shameless plug of some kind? I mean, comparing NetBeans to Eclipse and saying that these two points give NetBeans an advantage, doesn't make sense to me.

    Eclipse is pure java, too. Oh, unless you don't consider SWT to be pure java, and you prefer to have pure java Swing rather than the much nicer and faster SWT... so what if it's using the native OS interface instead of its own? I see that as an advantage, in any case.

    Eclipse can use Ant to build a project. I don't know if it's the latest version, but for all basic purposes, the version included is good enough. I don't know if there's an Eclipse plugin that automatically updates build.xml or lets you handle it in a graphical way, but I think ant build files are meant to be hand edited, anyway. You can use XML buddy inside Eclipse to validate the XML.

    And that stuff about using the NetBeans platform, sounds like the stuff Eclipse includes now with 3.0, where you can build your SWT apps using the same objects that make up the Eclipse IDE.

  3. Netbeans vs. Eclipse by fforw · · Score: 2, Informative
    Eclipse is pure java, too. Oh, unless you don't consider SWT to be pure java, [...]
    SWT uses platform specific libraries/DLLs, so the pure java claim for netbeans is not only technically correct but also in its meaning "running everywhere a VM is available".
    Eclipse can use Ant to build a project. I don't know if it's the latest version, but for all basic purposes, the version included is good enough. I don't know if there's an Eclipse plugin that automatically updates build.xml or lets you handle it in a graphical way, but I think ant build files are meant to be hand edited, anyway. You can use XML buddy inside Eclipse to validate the XML.
    Even the old 3.6 way of supporting ant was superior to the way eclipse handles ant scripts (integrating targets into the UI etc). The new netbeans 4.0 project system is really good. Ant is the project system so netbeans projects can be build without netbeans.

    There is even a wizard to import hand edited ant files as project. the ant files aren't even changed for that. beautifull.

    Netbeans can not only validate ant scripts it offers element completion for ant targets etc.

    And that stuff about using the NetBeans platform, sounds like the stuff Eclipse includes now with 3.0, where you can build your SWT apps using the same objects that make up the Eclipse IDE.

    .. with the only difference that netbeans had the seperate platform for ages and lots of applications are already using it.
    --
    while (!asleep()) sheep++
    1. Re:Netbeans vs. Eclipse by Anonymous Coward · · Score: 1, Informative

      • SWT uses platform specific libraries/DLLs, so the pure java claim for netbeans is not only technically correct but also in its meaning "running everywhere a VM is available".
      Gee, that sucks. I can only run SWT apps on Windows, Linux, Solaris, HP-UX, AIX, and Mac OSX? What am I going to do about Commodore 64 support!!?

      Seriously, I'd believe NetBeans support for Ant is better that Eclipse's in this new release (although Eclipse does support autocompletion for Ant tags). The built-in project builder in Eclipse can be a tad finicky. But that alone isn't a very compelling reason to switch.

      As far as the issue of the NetBeans "platform" vs. Eclipse's RCF (rich client framework), I'm working with both and I can tell you that the Eclipse API is far superior to what NetBeans has. NetBeans might have first mover advantage, but Eclipse has done it right(er).
  4. Re:market share ? by Anonymous Coward · · Score: 1, Informative

    Most java shops I've seen use IntelliJ Idea. It's the best IDE if you have the cash. Eclipse has a large group of followers among the OSS crowd but, in my experience, SWT's performance leaves a lot to be desired on !Windows environments.