Slashdot Mirror
Netbeans 4.1 Released
njcoder writes "Netbeans 4.1 was released a few days ago. Though it is only a short time since 4.0 was released and only a minor version number increase, the new Netbeans 4.1 contains a number of significant enhancements. New features include enhanced support for J2ME (mobile) projects, a new Navigator component, enhancements to the Ant based project system, ability to define multiple source roots, enhanced support for J2EE applications including EJB support for creating Session, Entity and Message Driven Beans, bundled J2EE application server, bundled Tomcat server upgraded to the 5.5 series, Web Services support, Eclipse project import tool, and more. The days of a slow and ugly Netbeans seem to be over. Using the new Metal look and feel in Java 5 brightens things up a bit as well. More information can be found in the release info and go here to download the new version. Java boutique has a review, with screenshots, of the new released titled IDE Wars: Has NetBeans 4.1 Eclipsed Eclipse?."
There must be something better out there. Am I missing some webapp debug tool for Eclipse?
Another thing: I loved the Search/Highlight feature (like the google bar). I think that this is fundamental for OO programming: you search for an object identifier in a piece of code and then you are able to quickly look at all the methods that are called on that object so you get an immediate feeling of what the code is doing to manipulate the object. Ecplise does not have that.
But it works, so I am using Eclipse.
As for the question: noup, NB is not eclipsing anything. It was about to eclipse Eclipse but it crashed yet another time and missed its chance.
C'mon, guys. An announcement of something is one thing, but this "article" is just a bunch of marketeering that would be more appropriate as an item under the "Advertisement" column.
Web application development is a lot easier for me in Netbeans. If you've never done any java web application development Netbeans is definately the tool. It's very well integrated into the system. Right after you install it you can start to develop, debug and test web apps. The bundled tomcat server makes the whole setup a snap. You can even set up breakpoints and watches in JSP pages. When I first tried Eclipse, I was very dissapointed that it didn't even have a JSP editor. I spent a day looking through the different plugins trying to decide on one. None of them (at the time at least) were free, at least not anything good.
The way IBM is marketting Eclipse seems to be mainly as a barebones IDE where other vendors can write plugins to sell to users. Meanwhile, netbeans comes with a lot more with the initial install. I tried MyEclipse but I didn't want to pay 32 bucks a year for something I thought should have been part of the package.
The refactoring support is a lot better in Eclipse though. You can install the RefactorIT module in Netbeans and get a lot better refactoring support. It's a commercial module with a free version that supports limited numbers of files. The pricing isn't too bad for the features you get and the Netbeans team is working on more advanced refactoring features.
From some blogs and news articles it seems like more people are making the switch to Netbeans now. I read something that stated there were 5 million total downloads of Netbeans since it's inception. 1 million of those were for versions 4.0 and 4.1. That's a pretty big leap starting with those versions.
Open Source Java DAO Generator
and I just did a search:
;)
Eclipse Sucks 155,000
Netbeans Sucks 11,300
Conclusion: More people think that Eclipse sucks more than NetBean.
I'm sure if you try you can come up with better criteria for evaluating Netbeans (a Java development platform) than its level of support for PHP.
Suck figs.
Sun has megabytes of unfixed bugs, but instead of focusing there, they are trying to compete with a highly successful, well-written free tool. This push for NetBeans ultimately comes from Sun's pathological desire to own and control everything: Sun absolutely hates the fact that Eclipse doesn't require their proprietary toolkit and that Eclipse can compile with open Java tools. Sun wants a desktop based on Sun Java, a server-side platform based on Sun Java, an office suite based on Sun Java, and an IDE based on Sun Java. It's really the same thing Microsoft is doing, only that resource constraints and public opinion constrain them a little more (e.g., they can't start a new GUI project from scratch, they just have to hack Sun Java into Gnome).
Eclipse is the only sensible choice for a Java IDE at this point: NetBeans may be a little better in some areas, and Eclipse in others, but those differences are minor. The deciding factor is that Eclipse has become the de-facto standard platform for plug-ins.
The heart of all this conflict really boils down to one issue: performance. SWT vs. Swing. Java developers have been debating SWT vs. Swing since the release of these two IDEs. More specifically, the debate has been about using SWT or Swing on Linux platforms.
One of the arguments against SWT is simply this: it's not part of the Java specification. SWT proponents argue that the responsiveness of a native application can outperform any pure Java implementation. Who is right? That is still up in the air, but it does seem that performance issues have at the very least leveled out, leaving the ultimate determination up to the other features of the IDEs
That's completely wrong. People like SWT not so much for the performance but for the fact that it acts like a native application. You get sub-pixel rendering on LCDs, and so forth whereas Swing is constantly playing catchup.
That Swing is part of the J2SE is a non-benefit. I'm using the IDE, not waging some holy war or caring about how it's implemented. I can't see how as an IDE user I would be happier with Swing because it is part of the J2SE.
dominionrd.blogspot.com - Restaurants on
If Swing behaves wrong its the PLAF which can easily be patched unlike all of these other toolkits, furthermore Swing 1.4 and higher has a new GTK look and feel and Java 1.6 will delegate rendering of GTK components to the underlying native system so its L&F in GTK will be perfect.
Cough... bollocks. The GTK LAF does no such thing. It's yet another "looks a bit like a native toolkit, but isn't... and is still typically ass-slow Swing."