Eclipse or NetBeans for RCP – That Is the Question
Rick Jeliffe puts Eclipse and NetBeans on the stand as he compares the two for Rich Client Platforms. At first, Jeliffe was not impressed with either. "I thought both were crap for the purpose - slow, ugly, immature, incomplete and bringing little but complexity to the table.” Now, he has changed his mind. "Both look wonderful for Rich Client Platforms. Eclipse has the edge if your market is the community of Java developers who probably have Eclipse already and your application can be made a suite-enhancing plug-in. Eclipse also has the edge if you want to provide a plug-in and a standalone version.
In defense of NetBeans, Jeliffe says, "NetBeans has the edge if you need Swing or all the OpenSorce libraries which use Swing— the wonderful SwiXML (which lets you specify Swing interfaces in XML, and uses reflection and the JavaBeans conventions to be very small and very fast) and the Substance look and feel library (whose Flamingo sub-project Topologi has contributed our BreacrumbBar control to) being high on my list."
Jeliffe goes on to compare other features such as documentation problems, SWT, wizards, etc. One question that seems to stymie Jeliffe is whether a Swing applet could be run in a browser page embedded in Eclipse. "I would say the decision tree for OS-neutral desktop applications would be something like:
Can we implement this using browsers?
Should we implement this using Java or Mozilla RCP?