Link Details

How can you compare eclipse to a program the only explores a directory? Strip eclipse down to do only that one thing and maybe it would be a fair comparison.

Not a bad article, but I voted down for the obvious attempt to spark yet another "Swing vs SWT" pissing contest with the remark about Eclipse -- seriously...haven't we moved past this kind of crap already? Comparing a simple directory browser to a full-blown IDE doesn't not a good comparison make (to put it mildly). And last I checked (which was fairly recently) Netbeans and IntelliJ weren't exactly speed demons either.

but I voted down for the obvious attempt to spark yet another "Swing vs SWT" pissing contest

Maybe it wasnt an attempt to spark a pissing contest, but a demonstration of the effort required to win it.

Not comparable at all.

Theres no flame war here, this is a post about code, 10 year old code and updating it and how thats pretty cool that it not only works but works really well. Its not an eclipse sux rant. There is a gratuitous sign off but obviously it would be ridiculous to compare a directory explorer with eclipse.

BTW If your not frustrated with your Java IDE you are working on insignificant projects

dcortez, yeah really. If you were going to do a comparison you should have compared similar code in SWT not Eclipse.

Apparently nostalgia is lost on some people? Load up the eclipse src tree in eclipse and call me next week when its done compiling.

SWT? Why would u compare anything to SWT? The first paragraph compares to windows explorer. Which is Win32 just like SWT, so same diff no?

You do realize there's a lot more stuff going on in Eclipse than just showing a simple file structure right?

BTW, I don't even use Eclipse but the comparison is completely unfair.

Well if waiting for eclipse to build for hours, while youd "just rather look at the file structure" and do some work is ok with you, then I guess your right.

Of course "I realize", I have to deal with this pain everyday. How is that fair? Is it fair that my development team has to drop down to text editors to get their work done because eclipse cant handle even medium sized project? This post was not an eclipse flame, but if you really wanna talk about how much eclipse costs in development shops, Ill be glad to provide you stats on 1-4 hour build times and crashing and unsound builds due to eclipse "method stubbing" in class files which you dont find out until its too late. I would estimate eclipse costs my shop somewhere around 20K a month in lost productivity. (But Ill switch to netbeans or intellij if you insist)

Uh ... I said I don't use Eclipse. I actually use Netbeans, but if you compared the Netbeans file "explorer" to this little program it would also be an unfair comparison.

"unfair" because netbeans is too slow?
,

I dont get the fair part. If you read the post, its about the code. Taking a few lines of the post out of context is silly.

The issue I had with the article isn't so much that eclipse/netbeans/whatever are good or bad -- they all have their issues and that's a good subject to discuss -- but that you spent a lot of time demonstrating getting some old code up and running and working well (which was well done as far as I'm concerned) and then suddenly threw a jab at eclipse, which really didn't have anything to do with what you demonstrated, or was only tangential to the topic you were discussing.

It just seemed out of place, and as such stood out to me and gave the impression you were blatantly trying to be derogatory toward eclipse/SWT. That may not be what you intended, but that is what I took from the article in the end.

Fair enough. Your right. As a minor explainer which wont get me off the hook, I have been using Eclipse and before that Visual Age for Java for many years, and I am very annoyed. Annoyed enough to start writing a Java IDE that will solve the issues that are annoying me, and yet not fall back into a text editor.

Point taken. I could have left that part out.