Comments on: Why Do I Hate Eclipse?

By: jim

jim — Sun, 14 Mar 2010 23:27:00 +0000

generally ok with Eclipse as free versatile tool – but somethings just strike me as stupid, like now — it acts like it opens a file but won’t display it — you have to make a “project” first — can’t use it to just take a quick look at some unknown new file. And, it defers to windows preferences — i ask it to open a file, i want to see how Eclipse views it, and it stupidly invokes some other tool —

i’m sure there’s some “logic” behind these annoying behaviours, just seems like the mindset is “you have to formally set me (Eclipse) up as the tool for some filetype AND don’t bother me with ‘little’ stuff i only deal with formal official ‘projects’” — well la te da… rigid mindless formalism at the expense of simple utility

stupid

By: Gregg

Gregg — Sun, 14 Mar 2010 06:03:00 +0000

Eclipse is so fucking slow and is a memory pig. It is painful to use. It is counter intuitive.

By: Greg 2

Greg 2 — Sun, 14 Mar 2010 14:20:00 +0000

1. Please be specific: what version of Eclipse are you talking about? What plugins have you heavily used? Is this Windows/Mac/xyz Linux? Generalized stuff is really hard to zone in on. I say this because I haven’t seen the depth of issues you have. Although I have seen some, each new release of Eclipse is better, more stable, and has better features. What else can I ask for?

2. I heard maven mentioned in more than one comment. I was just listening to “Maven without pain” episode of javaposse.com, and wonder if your problems are linked to maven.

3. For just about any project I have started, the first thing I code is the build process. Even if I have only written “Hello world”, I want a command-line script that builds the whole app in place before I start slinging tons of code. I don’t need to be running down problems for the build team. Using Eclipse as your build environment is dumb, Dumb, and DUMB! I use ant build my jar files. I want CM team typing “ant” on a prompt, NOT having the option to click 10,000 buttons and get it wrong through an IDE. However, I’m curious to see how the new Eclipse+Groovy JDT will be possible for an ant build. (HINT: I ain’t about to break into using the IDE for build jobs!)

4. You do need resources. That’s for sure. I have a 10-year old laptop that does NOT have the memory nor CPU to run Eclipse. Well…I get by without. Just using gedit with a command shell is fine. Some days, a nice big IDE with code navigation and searching is nice. Other days, I crave my nice, UNIX-y shell lifestyle I used back in college. #1 reason I like Linux is the fact that I have both depending on what mood I’m in. :)

5. Bottom-line: use what you like. Can’t speak to consulting engagements, where you probably have to meet your clients on their level. Maybe your first step is introducing an ant build job, and making sure they have a centralized code repository. That way, if your cranking code, you commit, they update, and you are nicely decoupled from them, and the code becomes IDE-agnostic.

By: Nicolas

Nicolas — Sun, 14 Mar 2010 17:56:00 +0000

I don’t know all IDEs… But from my point of view, Eclipse is a really good IDE for Java editing. But of course you need a decent machine to use it. I see the problem of 1GB machine… It is a shame when 4GB cost less than 100$.

Okay eclipse has some problems, like workspace mess, and all. But it also offer really good features :

- instant find a class, ressource
- call hierachy
- refactoring, code generation
- quick assist, auto completion, error correction, auto import, auto format
- local and SVN history
- server integration
- powerfull debugger
- good and fast UI (on a modern computer).
- it’s a standard… Like stated above, most editor have an eclipse plugin.
- it support many file format in standard, like XML with completion using DTD/XSD
- come with a complete framework for many things you need for software engineering… MDA and all.

I understand that not all people have to use the same IDE, and maybe some IDE are better than eclipse. But for now it’s free, you can use it on any operating system, and it simply work.

Of course, eclipse is a very heavy software, and the open source thing implie that if you use a bad coded plugin by some hacker, it will not allways work as expected.

By: Philho

Philho — Sun, 14 Mar 2010 21:46:00 +0000

Hey, it is refreshing to see an alternative opinion.
I do use Eclipse, after trying a bit NetBeans (haven’t tried it recently).
I use it at work: they can’t buy us some memory to go beyond 1GB, I don’t see them buying an IDE.
I use it at home: I just don’t have a budget to buy an IDE, even less an expensive one.
At work, it is problematic indeed, even more with our limited memory, even more if we ask it to compile our big project! (We usually use a command line Ant tool for this.) It is not unseen to wait to one minute or two just to display a tooltip I didn’t wanted actually… Auto-completion is a nightmare when you type fast, because it insists on getting a list of members when you already type the parameters…
Actually, I type most of my code in my fast, lightweight editor (SciTE) and switch to Eclipse for a quick check of the code (and auto-import feature) and debugging.
I experienced the bugs you mention above (still showing error in a corrected file, not finding classes in same package…) too.

Now, I am getting used to it (found it very confusing to learn, between projects, perspectives, views, workspaces, what’s not), and for some features it isn’t so bad… for a free software! ;-)

By: Mike

Mike — Sun, 14 Mar 2010 18:53:00 +0000

I think the best solution is to never mandate that developers use any one particular IDE.

Choosing an IDE is like choosing a spouse, there is no right/wrong/perfect choice. So mandating the use of a particular one is never going to make everyone happy, in fact, it will always leave a lot of people unhappy.

My projects were simple enough that we could store the core (source, config, libraries, etc) in SVN and then provide instructions on how to set up your project using the various popular IDEs. None of the IDE-config files were ever checked in. Since my projects were simpler, maybe this simply isn’t an option for everyone.

But if it isn’t, we should work to make it that way. Marriage of a project and an IDE has always gone badly every single time I’ve seen it happen.

By: Arturo

Arturo — Sun, 14 Mar 2010 18:52:00 +0000

> NetBeans is much better than Eclipse.

But Oracle will not support 3 different IDE-frameworks (JDeveloper, Eclipse, NetBeans)

By: Krzysztof

Krzysztof — Sun, 14 Mar 2010 11:33:00 +0000

NetBeans is much better than Eclipse. Integration with Maven and Sping and it is FREE! :)

By: Sébastien

Sébastien — Sun, 14 Mar 2010 10:01:00 +0000

The problem I talked about with M2Eclipse or SpringIDE is merely an example. But the fact that such bugs occur in numerous plugins (Subversive and Subclipse have their problems too by the way) is a good hint: the common denominator is the platform. And I have worked with Eclipse RCP, behind the curtain, and that’s where the whole problem comes from: it’s incredibly complex,, there are so many ways to do one thing, and the platform wants to be so generic, it tries to do so many things that it’s very hard to make it do what you want correctly.

Your “time and experience” remark is excellent, I would add patience to the mix. And what if I don’t WANT to? What if I just don’t have time to go through the learning curve to learn JFace and Eclipse RCP just to fix a product. I know, I know, that’s what Open Source is all about, that’s the deal: I get it for free and I accept to cope with a few bugs. But all I wanted to say with this post is “if you don’t want to cope with the numerous bugs, there are alternatives”.

By: Greg

Greg — Sun, 14 Mar 2010 04:23:00 +0000

I suppose Springsource like Eclipse because they focus on “common” in “lowest common denominator”. Others can’t get by “lowest”.

I don’t like Eclipse because it reminds me of all the programmers I’ve worked with who can’t code if you take eclipse away from them. One place I worked coupled their deployment process to Eclipse. Now that I think about it though, I’ve seen worse – at another place they deployed the JRE in the jar. I counted over twenty instances of the same version of the JRE on one server.