This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: NetBeans Users AstroTurf
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
There seems to be an underground movement amoung NetBeasn supporters to astroturf in several forums FUD statements about Eclipse-IDE. Statements such as:
1. EclipseIDE does not have J2EE support.
2. EclipseIDE is slower than NetBeans.
So lets us bus tup this FUD!
1. A project to proivde free j2ee support was started as Lomboz in 2002 according to the old project sitesourceforge.net records. First version was released 2003 for the EclpiseIDE version 2 series. During the saem period Sun Microsystems was trying or attempting to get NetBeans users to pay for a j2ee plugin(duirng 2001-2002 I was a Netbeans users suffering without free j2ee plugin support).
During the Eclipse2.1 ramp up the idea was floated to have Lomboz, which moved to objectweb, code donated to the Eclipse project. Thus in EclispeIDE 3.x at first you did aseparate download a of free j2ee support plugin from at first from objectlearn.com, the authors of Lomboz, and then later from objectweb.
As of EclipseIDE3.1.x Lomboz has been part of a project from Eclipse as full j2ee support inclduing cod donated by IBM. Given the almost 100 press releases abotu the code donation and that project at Eclipse its kind of hard to fathom that Eclipse 3.x users are nto aware of the J2EE support. An dof course, SUn finally figured out that Netbeans users were not interested in paid j2ee support plugins.
2. During the changes from EclipseIDE2.x to EclipseIDE3.x way of doing things a new method for deploying EclipseIDe was recommended by the Eclipse project. They deeemd it so importnat tha they included the directions in how to do the new deployment methods in the user manual.
Basically it recommends that to allow easy portability and updatability that you arrange out your stuff into separate folders such as non specific/optional plugins, workspace, and etc and use the new feature to point references to plugins, workspaces, and etc to stufff outside the root eclipse folder. The result is no speed difference between Eclipse2.x and Eclipse3.x when machine speed and JDK used is the same.
In fact, both startup times and UI response seems to be 50% faster than Netbeans even when using updated versions of both products.
I will not talk much about NetBeans Eclipse project import but simply to state that during Netbeans versions before 4 they thought so wisely of the Apache ANT project that NetBeans did not support the Project definition standards emphasized by Apache ANT project until version 4. Given that ANT was somewhat started at SUN, is that not a glaring oversight in design? Maybe the emperer has no clothes?
Previous Topic
