Skip to main content

Dr. Dobbs Writes About Eclipse and Netbeans

The August issue of Dr. Dobbs carries an article about Eclipse and NetBeans titled "NetBeans 4.1 & Eclipse 3.1" by Eric J. Bruno. The article is a good, if high-level, comparison between the two. Eric is apparently an Eclipse user, as he admits that
I first used NetBeans for Java development about two years ago and wasn't entirely comfortable with it. Consequently, I began to use Eclipse. With it, I could develop and debug Java code within a full-featured IDE that didn't feel clunky.
That was pretty much my first reaction to using NetBeans prior to version 4. I've been a user of Eclipse essentially since version 2.

The article starts by introducing the reader to overviews of NetBeans 4.1 and Eclipse 3.1. The author then compares and contrasts how both IDEs support J2SE development, J2EE development and J2ME development. The author's conclusion is pretty much dead on with mine at this point in time:
Comparing IDEs such as Eclipse and NetBeans is similar to comparing development languages - there is no winner. Both IDEs are competent development platforms for J2SE, J2EE, and J2ME development. Choosing between them largely comes down to taste, influence by others, and whether you develop in other languages in addition to Java.
If you're into using either platform for rich client development then it will also come down to what widget set you want to use. Many strongly claim that the only way to develop client facing applications is to use the Java Foundation Classes. If that's your view then you'll want to use the NetBeans Platform as your rich client platform as well as your IDE. Others will like the fact that the Standard Widget Toolkit and JFace underpins the Eclipse rich client platform, and uses the platform's widgets on which it runs to provide a look and feel that matches native applications. I happen to fall into that camp. For those of you who believe that JFC is the Only Way, let me remind you that Sun has spent a lot of effort to make JFC play nicer with platform native widget sets, especially Gnome and Windows. There appears to be a rather vocal minority in the JFC camp who want a native look on the platforms they deploy on. And somebody liked the Eclipse SWT look and feel so much on Windows that JGoodies created the JGoodies Windows Look and Feel.

Besides, it isn't the look and feel so much that separates the two toolkits as the architecture. I for one miss features in Java2D that are missing in SWT and JFace. Even I find it a difficult choice. Both IDEs are excellent, both platforms are excellent, and to give Sun its due, the new look and feel for JFC is much better than the older metal, which I came to hate with a passion. And for the goombah on JavaLobby that compared IDEA with Eclipse and NetBeans, learn how to write a better comparison. Your review reads like a stoned idiot wrote it.


Popular posts from this blog

cat-in-a-box channels greta garbo

So I'm sitting at my computer, when I start to notice a racket in back. I ignore it for a while until I hear a load "thump!", as if something had been dropped on the floor, followed by a lot of loud rattling. I turn around and see Lucy in the box just having a grand old time, rolling around and rattling that box a good one. I grab the GX1 and snap a few shots before she notices me and the camera, then leaps out and back into her chair (which used to be my chair before she decided it was her chair).

Just like caring for Katie my black Lab taught me about dogs, caring for Lucy is teaching me about cats. She finds me fascinating, as I do her. And she expresses great affection and love toward me without coaxing. I try to return the affection and love, but she is a cat, and she takes a bat at me on occasion, although I think that's just her being playful. She always has her claws in when she does that.

She sits next to me during the evening in her chair while I sit in mi…

vm networking problem fixed

Over the weekend I upgraded to Windows 8.1, then discovered that networking for the virtual machines wouldn't work. Then I tried something incredibly simple and fixed the problem.

Checking the system I noticed that three VMware Windows services weren't running; VMnetDHCP, VMUSBArbService, and VMwareNatService. VMware Player allows you to install, remove, or fix an existing installation. I chose to try fixing the installation, and that fixed the problem. The services were re-installed/restarted, and the virtual machines had networking again.

Once network connectivity was established there was exactly one updated file for Ubuntu 13.10, a data file. This underscores how solid and finished the release was this time. Every other version of every other Linux installation I've ever dealt with has always been succeeded by boatloads of updates after the initial installation. But not this time.

Everything is working properly on my notebook. All's right with the world.

sony's pivotal mirrorless move

I'm a died-in-the-wool technologist, even when it comes to photography. I have always been fascinated with the technology that goes into manufacturing any camera, from the lenses (optics) through the mechanical construction, the electronics involved, and especially the chemistry of the film and the sophistication of the digital sensor. It's amazing that the camera can do all it's asked of it, regardless of manufacturer.

Of all the types of cameras that I've really taken an interest in, contemporary mirrorless (again, regardless of manufacturer) are the most interesting because of the challenging problems the scientists and engineers have had to solve in order to build a compact but highly functional camera. In particular I've followed the sensor advances over the years and watched image quality climb (especially with μ4:3rds) to exceed film and rival one another such that there's very little difference any more as you move from the smaller sensors such as 4:3r…