As a consultant, I’m very often forced to use Eclipse as a development environment, and every time I do, it’s such a pain for me that I can’t help complaining about the poorness of this thing. And every time I do, most of my team mates, who have been brainwashed by the monopolistic propaganda of Eclipse, just keep asking me what’s wrong with it. And sometimes it’s hard to explain because it’s really a matter of user experience. And each time I find a specific example, I get answers like “yeah, but that’s just one thing”, or “I’ve never had that, you’re not lucky”, or “this is just because you’re not used to the Eclipse way of doing things”, or even the worst one “maybe yes, but it’s free!”. Since when is “free” a feature?

Right now, I’m reading the SpringSource dm Server getting started guide, and I was very surprised to read that SpringSource guys, who aren’t exactly stupid, and seem very experienced with Eclipse itself as they have based all their development tools on it (Spring IDE, STS, etc.), talk about what they call the “Eclipse Dance”. I didn’t know about the expression but I’ve definitely danced it more than once: every now and then, Eclipse views get all mixed up, some views indicate errors in a file, while other views on the same file say everything is OK. Or you get a message saying that it cannot find a class where you have the source in front of your eyes. Or like now, I have 2 maven projects at the same level referencing the same parent POM, and one of the projects says it can’t find the parent artifact, whether the other one seems to find it without problem. And when that kind of things happen, the only thing to do is to try a combination of closing all projects and reopening them, clean all projects to force a clean build, or even restart the whole Eclipse workbench. WTF?

How can SpringSource support such a poorly designed environment while admitting such unacceptable bugs? Oh yeah right! It’s free, so everybody uses it. This is really the perfect example of when Open Source can also kill innovation instead of fostering it. It’s free so everybody uses it, including corporate customers, so all tool vendors base their tools on it (Spring IDE, Flex Builder, Weblogic Portal Workshop, etc.), so even more people use it (even if they have better tools in their bag), and we’re screwed.

I would love that framework vendors focus first on command-line integration with tools like Maven and Ant, and then provide IDE integration for a few popular environments, including Eclipse, Netbeans, and my personal choice, IntelliJ IDEA. This would reinforce competition between IDE vendors instead of killing it while considerably lowering the barrier to entry to their frameworks. Right now, SpringSource is lucky I really need to understand more about dm Server, because if it had been only for cusriosity’s sake, I would have given up already just because of the tight integration with this crappy Eclipse thing and all the pain I have to make it work consistently.

So if you’ve already been in that situation, and you start to think there’s gotta be a better way, try out IntelliJ IDEA.

PS: I’m not related to Jetbrains in any way. I just happen to be a very happy customer of theirs, happy to pay a few hundred bucks every year to get their latest version, because as a Jetbrains guy said it last year at Devoxx, “IntelliJ iDEA is the only IDE worth paying for.”


Johnny · January 28, 2013 at 6:47 am

I agree. Eclipse is a pain in the neck. Actually, all free software is bad. We are forced to use free software because most software companies won’t spend money on any thing. If our cars were to be paid for by advertising, they would be just as bad.

    solusrex · October 10, 2014 at 5:13 pm

    Linux is bad ??? Vim is bad ??? Emacs is bad ???
    GNU suite is bad ?

    ALL free software is bad … only clueless person who never saw anything but REALLY bad eclipse can say that. Eclipse IS bad … more .. it sucks ! because its based on bad architectural decisions — not because its free

Bernard · March 6, 2013 at 9:09 am

Switch to NetBeans and support the team to fix their debugger :) After that, you will never look back.

    ramdane · May 4, 2014 at 1:58 pm

    That’s it you’ll never look back … unfortunatly sometimes we are forced to

    Stu M · September 18, 2014 at 11:47 am

    That’s amusing: “Switch to netbeans, it’s better except for this one thing, so if we get them to fix it, it will be better than eclipse but switch to it anyway.” :-)

VipHaLong · March 27, 2013 at 1:01 am

Well, I used Netbeans first when starting to learn Java, it’s really not good as what I can receive from a standard IDE like Visual Studio, however it does work well enough. Now I’ve tried using Eclipse and it’s even really worse far compared to Netbeans, It’s too buggy, its wizards are for nothing. There is a very annoying bug which always show a message box saying “Unhandled event loop exception” with 2 buttons: OK and Detail, clicking OK will show another message box with 2 buttons: Yes and No, clicking Yes will restart Eclipse. This bug happens often and always occur when I click mouse on the editor. Another nasty bug is letting it idle for a long time with some opened project, it can use my CPU up to 70% with a non-clear reason? At that moment, it’s really freezed and have been out of control and need to be restarted. I think I’ll go back to Netbeans, at least Netbeans can help me work better although it has some unsatisfactory features (but not really important). Please continue sharing your idea here…

jb · March 27, 2013 at 12:46 pm

Couldn’t agree less! Eclipse is the most unintuitive IDE I ever used. Jetbrains have a free community version of Idea now too, so you only pay if you want enterprise features in the Ultimate edition. I am not affiliated with Jetbrains either but I have been using it since version 6 (after JBuilder died out) and never looked back.

    Ungo · August 26, 2014 at 7:21 pm

    You couldn’t agree less? So you don’t agree at all?

Pete · March 29, 2013 at 5:06 pm

It almost feels like people have gotten so used to eclipse sucking that they’ve forgotten a world when IDEs didn’t suck. I will give the opinion that when an IDE is so terrible it actually affects the architecture of the app (Like which maven plugins I use)… Then that app is no longer acceptable. Ive actually not used certain eclipse plugins because of lame eclipse m2 errors. When people talk about loving this app and thinking it’s great.. I almost think this must be the same group of people that think cell phones work great. Just because a tool has the potential to go from point a to point b doesn’t mean it’s a hero. This app sucks.. And because everybody uses it Im defenseless… Or I get the be the only guy on the team who doesn’t use it with all the political lame that doing that causes.

No… Eclipse sucks.. And this guy is right. Free isn’t a feature.

pete · March 29, 2013 at 7:36 pm

One more comment.

I admit this app works great for JavaScript. Because I tend to edit the files in eclipse and don’t do lengthy command line builds outside of eclipse. The issue comes when things on the disk are changing outside the IDE. Like when doing a huge re-build all maven build. I’ve got no problem with pushing refresh and clean and rebuild all… Well I could live with it if it wasn’t so prevalent. And things like Maven need to be directly supported. I spend all day making a maven file work slick and find out half the thing errors out because of lame things like “unrecognized phase ‘copy-dependencies’ not recognized by .m2”. Which is utter nonsense. It even comes up in the Eclipse smart edit!!! So why do they not support it!?!?! What do they care.. They call maven and the thing works in their own editor. Yet they force an error message that makes several plugins like the debugger complain about thing being in an “Error’d state”.

And the entire notion of caching the dependencies needs to be totally re-done. Most people complain about the “refresh” “clean-all”, open close the project restart the ide experience that is Eclipse. Have you ever done the above and then had the entire workspace get deleted!!! I sure have! About 20 times in a 4 year period. The issue is so lame.. Ive gone to .project files with embeded variables so I can easily import them again when the “good bye workspace blues” happens. Not that I don’t love marching through 20 dialogs to reset them.

And speaking of resetting settings… Make them all in the same friggen area!!! Enforce plugins to do the same!!!

Then there’s the whole improper defaults. Don’t make me res et my virtual memory settings to something that’s reasonable. Just do it… Black box. And I don’t want to learn eclipse like Im on the dev team to make it work. Just make it work. No excuses. Make it work. Everything that comes.. Set up correctly. No errors. Make it work. I don’t enjoy having to google for 40 mintues about which file eclipse keeps this in. I just want ISuck=false setup Right out of the box.

Coordinate your plugins. On the mac you don’t recursively find projects that import (At least in the latest Version: Juno Service Release 2 Build id: 20130225-0426 you don’t). But the maven plugin works fine.! ?!?! The maven plugin by the way.. Wont let you turn off auto scanning so if I use your maven editor the whole workspace trys to auto rebuild and refresh it’self as Im typing in the pom.xml when the pom.xml is a parent! It’s most annoying. Annoying meaning I have to restart the entire IDE at times to stop it. With a time loss of about 15 minutes before im up rebooted and back in the same file again. Because.. When it restarts I almost always have to do another refresh, clean all, rebuild all again… Even though the ide just closed in a state where it reported that everything was fine. All I was doing was editing an xml pom.xml file. I didn’t expect dynamic build alls to cascade down the ide with every type. So.. I have to edit eclipse files in the text editor with no smart edit! Wow.. That sucks.

Ever had the ide install a plugin and break the ide.. I have! I wont go on about that Ill let the statement stand. Their plugin’s broke the ide by installing them with default options. Uhhhhhh!!! That’s a guy not even bothering to run his code when the vanilla method was chosen and it pops every time. That’s like “smack upside da head” bad.

Then there’s the customized versions of eclipse like SpringSource. Well that creates confusion and is irritating in a work force. “Works on my eclipse” type problems between co workers.. Always followed with “Well what version of eclipse do you have!!!” Ughhh.. One ring to rule them all my friends. On ring that everyone uses gets better over time and contains all the plugins which I can use or not. Id rather have more on my hard drive then the “Which version are you running because the plugin works fine for me lame-ness”!!!

Never ever mutter the word “It’s free so sucking is great”. If your going to push your IDE as the defacto dev standard for the opensource java community then you’ve taken on a huge task and that requires responsibility. Have some work ethic. Sucks because it’s free is a super stupid copout. And you set the bar for other apps and UIs as well. So sucks becuase it’s free in your case is creating a paradigm. And that isn’t free. Not to the dev community it isn’t.

Ok.. That’s all my “few” complaints. But as people on here say “Works great” I love this app. Well I also take the bus if I have no car. But that doesn’t mean I love the bus. It takes the bus 2 hours to get to work so I started riding my bike which takes 40 minutes. Sometimes a tool becomes more a liability then it’s worth.

By the way as someone else mentioned netbeans is free and they support maven right out of the box. And because they are the new commer alternative at this point (althought they’ve certainly been around) their attitude seems to be “Lets get right on that” as opposed to “It’s free, so suck”.

Tim · July 25, 2013 at 4:20 pm

I’ve been using Eclipse for a number of years and I’ll probably keep using it. I’ve tried NetBeans a few times but found it more like a collection of Hepler/Wizards than a IDE. In my experience it was also slower than Eclipse. The re-factoring also sucked. Which is an important feature if you work on any project bigger that a few files. It also relied on external build systems. So the error and warning reporting can never be as complete as what Eclipse gives. This also limits NetBeans ability to do auto-complete for variable/method names.

NetBeans may have improved in the last few years, but my impression was it needed some serious architectural changes to do what Eclipse has done from the early days. Integrate your Development Environment.

One of Eclipse’s key features is also one of it’s biggest weaknesses. That is it’s extendibility. I agree the Maven plugin still has problems with multi module projects. But it should be noted that this is a problem with the Maven plugin and not Eclipse. So I ask: Is there another IDE that has perfect plugins? Clearly if you think yes then you are deluded.

Lothar Schwab · August 13, 2013 at 5:22 am

I am using eclipse for about three years now. It was not a pleasant experience. For the last year we are using the eclipse maven plugin. It drives me nuts. We have in excess of 50 maven modules. When I just automatic build eclipse often completely hangs up (completely CPU bound) and never finishes the build. It is happily building who knows what over the entire weekend and still not finishing. When I turn the automatic build off I can at least write code. But when I try to start anything the stupid thing is 100% CPU bound updating maven dependencies for 10 minutes. Then when it builds it gets totally hung up – also for 10 – 15 minutes at times. What is the maven plugin doing? Why does it take trillions clockcycles to set the stupid classpath containers? Why does it take trillions of clockcycles to build a few thousand java classes?
And gosh I hate it if it builds endlessly and I dare to save a source code file. Then it always hangs until either the build finishes or until I loose my patience and kill the damn thing.
I totally 100% agree with what somebody wrote earlier in this thread: eclipse is OK to for small projects – but when dealing with really large projects eclipse is not the right tool for building – at least these are my observations.

Anatol · August 24, 2013 at 1:49 am

Eclipse is a very bad tool even for small projects.

Ilya · August 26, 2013 at 3:02 pm

@Kt, I absolutely agree, Eclipse is a cancer, there only a few vendors which got quite right. For example, XMOS uses it, but they also provide decent command line tools. Meanwhile, TI’s CCS totally sucks – the CLI build tools are actually a headless eclipse… I have managed to dig out the MSP430 compiler at the end, but it was well hidden. ARM’s DS-5 seems to be not too bad, but I haven’t spent much time with it yet. The worst one is probably NXP’s Code Red, which is essentially GCC+Eclipse that you are asked to pay for. May be Mentor Graphics has done a fairly good job at some of the features, although I haven’t yet fired it up and not too sure how much would they actually want me to pay if I do kind of like it. Although, Microchip seems to have a better solution with Net Beans and separate compiler packages which now support Linux and OS X, but I don’t get to use PICs at all. Ah, almost forgot Atmel’s skinned version of MS Visual Studio… the latest installer you get from them is actually corrupted, but it took me half a day to figure out and then it’s a pile of windows bullshit anyway, while GCC+avrdude is way easier to use for me anyway.

Angry · September 7, 2013 at 4:31 pm

I use eclipse for Android development and these are the biggest problems which I have not resolved:
1) when using libraries and doing run as, the application pushed might be not the one which is being compiled and an older version is pushed to the device

2) just suddenly all my keyboard shortcuts stop working or are working in a different window than I really am (I guess this is some kind of easter egg) only restart of eclipse helps.

3) suddenly my Undo stops working. only restart of eclipse helps.

4) slow as …. fill yourself. I don’t understand why switching a java or xml window should take more than 2 seconds on years HW (SSD, 8gb ram). it does in eclipse. tried every hack which I could find – not resolved.

I am greatful google created the intellij android studio and I can leave eclipse as soon as possible.

db · October 14, 2013 at 8:12 am

eclipse is the stupidest IDE and it always was, nothing but a piece of crap, sucking memory, being so slow, counter intuitive. I have used it on and off for years and have noticed zero improvement.
It was always a piece of crap.

ArkosX · October 24, 2013 at 12:11 pm

Eclipse is a Mess, and now I see that even in things I don´t use at all, after reading the posts.
It is not “user oriented”; It is not for the way a guy would use it, it is a tool for developer of the Eclipse too. It is a patch over patch (the problem of collaborative development that cannot be solved if there is not quality control, usability testing, so on) .
There is no encapsulation; one has to know about everything (and that is a lot of letters: RCP, SWT, OSGI, e4xmi, JFace SWT, WTF…, Application Model, injection). For a basic program probalby you need to know 100 classes and be an Eclipse architecture insider -other IDEs would be 10-.
-Do you want to set the height of a row in a table… create a listener…;
-you want to capture the event when a tree collapsed? after collapsed? program a job (thread) -an learn what the heck are the several classes you need to use in between-.
-“modules” configuration(s)? easy, check the build paths, general and for each project (curious concept of project in this IDE), ey, remember you have the manifest, the plugin.xml, the product, the run configuration… As a developer I don´t care what are the reasons why historically there are 15 conf files in different places in the project tree, I just one one place where to configure everthing. But it’s ok, is very intuitive, if you simultaneously press the “A” Ctrl, left with the toe, and fart over ESC, then wadawum! it magically did something that makes that illogical error disappear.
-Overhead, that is time spent in solving IDE issues instead of creating functionallity, I would say between 25%-75%, depending on the experience of the team.

-Learning curve: years. In other words, only if you are one of the Eclipse Gurus you can keep up. I think this is what will kill Eclipse at some point. The time you need to train people in Eclipse goes far beyond the price of comercial licenses of serious IDEs. btw, interesting comparison of Eclipse-based comercial IDEs, shows a net improvement cost of between 14% and 35%. In other words, that is the waste of Eclipse because things are not as good as at least I would expect. This is an study of 2007.
As the post started, “but is free”. Well it is not free.

BTW I loved when one of those Gurus said, showing WindowBuilder in a expensive class, “isn’t it cool?” meaning the creation of windows graphically. Guys, this was solved already in 1998 in C++ IDEs, and I JBuilder or NetBeans little bit later.

I’m kind of pissed off, aren’t I?

So guy, iof you are reading this thread, be aware, if you are checking out what IDE to use, be sure Eclipse is the only alternative you can use. Ah, and if you are not dealing with services in the sense OSGI (99% wont), then forget about plugins, use the old fashion jars.
BTW, personally the problem of discovering bugs runtime (vs. C++) gets even worse with Eclipse.

And I feel that the supporters of Eclipse are those who have only workd with Eclipse -since the time they learned in class or by their own, because it is free. And then got into the sickness; nobody like to leave aside what has cost a never ending amount of hours learning.

I give Eclipse, that it is extremely flexible, but that flexibility would only pay off 1/1000 of your projects and only if you are an Eclipse guru.

PS. Yes, I love the naturalness a guru in a teaching session, said “yes, ok, you just have to restart Eclipse to be sure”.

Joe · November 7, 2013 at 11:33 am

Working on android projects, i often come here.
Reading comments about eclipse is both a psychotherapy for me and a life saver for my (innocent) laptop.
Wanna get back….gimme back Borland Turbo IDE :(
//Yep, im old

Joe · November 7, 2013 at 8:52 pm

Yes, I think I would prefer using vi, xedit (mainframe), or even a card punch again before I’d go back to Eclipse. Thankfully I’ve been given the latitude to choose alternate IDEs.
-Another old Joe

ArkosX · November 7, 2013 at 10:51 pm

And what about Turbo Pascal! I have an MS-Console-based (but somehow graphical) scientific calculator (better any I’ve seen ;) ) which I did with about 2000lines of code developed in two weeks of Chrismas time and that I still use! Same thing in Eclipse would be 200MB 6Months, and I wouldn’t even understand some parts of the code (copy and paste from internet snipets)…
After Builder, I complained about the usuability -programmingwise- of MS-Visual… with Eclipse I miss any. Yet I never liked vi neither :P

Joe · November 8, 2013 at 4:20 am

Yeah… the old good Borland Turbo compilers…
F9 and thousands of lines compiled in a snap on a 386 (on a 640kb 8086 as well)…
yesterdays eclipse footprint: 1.2 Gb RAM :D :D :D

Eclipse should be sponsored by coffee machines producers, they are directly involved in the project life cycle:

launch IDE: coffè break
clean project: coffee break
launch (so called)debugger: coffe break…no, maybe lunch break.

And what about not shutting down a 5000Mips+ PC to avoid eclipse restart? lol

wanna go back…
i know… im old :P

ArkosX · November 8, 2013 at 3:10 pm

I loved the comment about sponsoring.
8086, no hard drive, I developed that tool in 1993(just before getting my wonderful 486DX2).
BTW, I even checked a fortran compiler from the 80’s… which obtained faster applications than the C compiled ones. we are going backwards! LOL
If that is the trend,m we got a Winner, eclipse, it goes several years before the rest!
Seriously guys, what are we doing wrong! Why people don’t realize about Eclipse? I have no doubt programmers are better than I never was but IMO they just are too inside Eclipse IDE instead of looking to what non-IDE developers need and productivity.

Joe · November 8, 2013 at 8:41 pm

The real question is “why aren’t there better options available?”

Sébastien · November 8, 2013 at 9:28 pm

There is a much better option, an option worth paying for: IntelliJ Idea

Joe · November 9, 2013 at 5:40 am

Regarding android development, despite all, Eclipse is the only IDE that provides a tight integration with the android sdk.
A “new” product called Android Studio is actually under development by google (early releases are available) but version 1.0 is yet to come. This time the IDE is based on IntelliJ.

By the way i think the performance and memory issues will not disappear with the new IDE.
I think the main problem of all these editors (or IDE) compared to the ones from the pase can be identified in the following 2 points:

1) Too much automation: auto complete auto compile auto buildup auto everything: this is absolutely unnecessary and
counterproductive especially for experienced coders and/or small projects, i know tere are a couple of hundresds of switches deep in the preferences boxes but this is not the main point, the main point is:

2) Java…these IDEs are written in java.
For its nature java is a platform/language that produces slow, memory hungry, uselessy overthreaded applications.
Despite i consder java a beautiful language and despite the reassuring comfort of having a comprehensive api available this is a fact.
Just compare a java written desktop application (of any kind) with its native counterpart and you will see the difference, huge difference.

Java is a (big) problem for desktop application. Full stop.
It has many advantages for server side, multiplatform and blah blah…it’s easy but it’s incredibly slow compared to a standard native application.
This is because Java is not just a programming language: every executable brings with him an “operative system”, the jvm, that must be embedded in a single process (from the real operative system this time).

It should not be used for high performance desktop application, once upon a time a text editor for a programming language would never have been considered an “high performance” application….it seems that times are gone.

That’s why i don’t blame eclipse guys, jokes apart.
Of course as a technician i don’t like the academic flavour of that software (the search box design for example is something completely beyond me…something i will never understand), but i don’t think this is the point.

To get a proof just try to fireup visual studio from microsoft….check the speed and the memory consumption…
no way to compare with smt like eclipse or others java based stuff…would be like challenging Bolt in the hundred meter dash. No way.

Borland itself, the producer of the best IDEs of the past (not only dos based turbo xx but complex visual RAD like Delphi as well), when they tried to develop a RAD/IDE in java, JBuilder….same performance issues, same unacceptable slowness, same for Oracle one (was based on jbuilder), IBM Websphere and all the others.

So the real question is: why do they develop these pieces of software in java ?
The answer (imho) is: because is easier, simpler, faster and above all cheaper developing in java than using a native language.
I think they do write these sysem in java because there’s no valid alternative with the same advantages.
Where there’s an alternative java is often left behind because of his weaknesses (just think about jsp compared to php for websites).

Most of new gen coders are java guys, they study the language @ university or they learn it directly while working on theyr first project, the average java programmer is often not an hardcore technician (like for instance a c++/asm coder), often coming from academic environment, not caring about optimization, in short a completely different profile compared to a 1990’s demo coder (this would explain the eclipse search box).

I think this is not so bad because computers are now much faster that 20 years ago,
i used to code in asm 20 years ago….now i dnt need it anymore and i think its ok, the world goes on, given that java seems to be the fastest and cheapest way to develop this kind of software, i think it’s good they’re using it.

I think The real problem with java is a decent option for native applications, i think this is more a business/political matter than technical, but i will talk about this in the next comment if your’re interested to this discussion ;)


Paulo Goncalves · November 28, 2013 at 9:54 pm

Man! Finnally i can say i am not alone in this universe! thanks God. I am a bullying victim guy in my work because i compare Eclipse to shit. It stinks so much i can stand it …

I use 2 different IDE. For every Java Projects, NetBeans. For Android stuff, definitelly, IntelliJ. If in sometime could be possible to mix the two i am forced to say we could see the best IDE ever.

Netbeans is simple and do the job. Period. Inttelij is smart. Easy. Logic. And do the job.

Why in the name of GOD, that shit-makers of Eclipse Foun(fuck)dation want to say with Perspective??? I have on perspective to write my fucking code and put it to work.

Why to use a IDE that to do the basic we have to install plugins from all the known galaxies? Why?

Joe · November 30, 2013 at 2:29 am

I was forced to use eclipse for many projects and I don’t want to waste my time talking about it anymore. IntelliJ is a very productive IDE and I love it.

Thomas W · December 12, 2013 at 1:29 am

Eclipse power-user, for me IntelliJ is weak in refactoring & misses my single most-heavily-used one (rename in file).

I also like separate Debug & Synchronize perspectives, IDEA is weak & underpowered in these areas.

Eclipse is not perfect, granted, and there are some wrinkles especially with Maven subproject support.

ArkosX · December 12, 2013 at 10:37 am

Thomas, IME, making refactoring easier leads to: “OK I can do whatever shit because I can always refactor it”; which leads to the worst possible code which works (TDD vs. MDD). Plus technical issues leads to refactoring not treated accordingly by the repository when updating/committing.
Perspective I feel is a cool thing that some people or some cases can be useful; the problem is that Eclipse forces every single one to use them. A level of complexity unnecessary if you dont use that, plus so much flexibility makes that perspectives are not same across users -without user knowing he is changing its perspective.
BTW, I do not like the debug perspective; everything changes, and I want to have all the same as I am coding, having only a couple of views more but embedded in the general layout. So, ok, a perspective idea is good, and if you want to use it learn about that, if don’t you shouldnt need to learn anything about that and it shouldn’t get other things more complicated.
As I said Eclipse is very flexible, but that introduces a huge slope in the learning curve many times unworthy because I dont use or want to use other characteristics. It is so flexible that it is a mess.
For how long have you been using Eclipse, and IntelliJ? other IDES? Other languages?. That helps in order to appraise your positive answer about Eclipse.

ArkosX · December 12, 2013 at 10:42 am

BTW, here it is the old comparison between Eclipse and other (Eclipse-based) IDEs.
Wish there were something more current, but since Eclipse has become a monopoly, like any monopoly harms the customer, but also makes that less people look “out-there” to compare.

Diego Alberto Arias Prado · December 23, 2013 at 8:59 pm

I am working in a project in which I have been gently forced to use Eclipse. I do hate it.

Eclipse often hangs, which I find surprising given that NetBeans, my IDE of choice, hardly does it – and it is a pure Java application.

It is not just that hangs, I also find it unintuitive. It seems a large set of fat plugins that are poorly coupled.

But the worst of all is not Eclipse itself, but its legion of fans.

Most of Eclipse fans seem brainwashed beyond any possible recovery. They are unable to understand that you just prefer another IDE: NetBeans, IntelliJ IDEA, whatever. Just show them that their so much adored IDE does not work, and you will be answered “Sh*t happens!” and, after that, you will be encouraged to keep on using it.

SamyR · March 10, 2014 at 10:37 pm

yeah, eclipse just sucks. It’s such a memory hog or memory black hole to be more precise. It’s monstrous with thousands and thousands of options, sub-options, configurations. I don’t understand why any experienced programmer would even need eclipse. If you HAVE to use IDE, try NetBeans. It’s little bit better than Eclipse.

SamyR · March 10, 2014 at 10:39 pm

Lot of programmers don’t like eclipse and it’s more common than you think. And lot of those who say they are ok with eclipse are saying because of fear of being looked upon as stupid. Classic case of Emperor as no clothes.

Maxime Poulin · March 12, 2014 at 3:53 pm

Complaining about maven project handling….
Come on dude, you are complaining about a plug-in.
So complain about the plug-in, and the people who coded it.
I’ve been using eclipse for the past 13 years, and honestly, after living with Notepad, then Symantec Café, Café Lite, Visual Café, Visual Age for Java, JBuilder from 2 to 6, well Eclipse is definitely a good tool.

Now for the plugins, well third parties. Will you say that Android is bad because some apps are not working well ?

So I do not agree.

Yannick Majoros · March 28, 2014 at 5:30 pm

Same here. Using Netbeans, much better, more features. I love the fact that it does maven right: building a project is *just* mvn install etc. Eclipse has its own config and tries to maintain it in parallel, and it hardly works.

I’m more an Eclipse hater than a Netbeans fanboi. I did use jdevelopper (yes, I’m one of the 6 happy users which did). Cool work, but nobody uses it. I’d use Intellij if it was better than what I get for free in Netbeans, but I didn’t experience that yet.

In all cases, Eclipse does to much things wrong. Should be rewritten, but it’s just a bunch of plugins with no plan, changing a bit will break everything. So, they stick with their own config besides maven. Enough for me to never use it again.

anthony305 · April 2, 2014 at 11:59 pm

Eclipse: the only IDE that doesn’t show the version number but requires developers to root through properties files. Eclipse developers need to man the fry station although I think they might fuck that up as well.

Vikas Nigam · April 13, 2014 at 2:51 am


Thank you for saving me from the mighly Eclipse as I was looking for making a choice between Eclipse and IJ.

IJ it is!!


Chris · June 17, 2014 at 4:08 pm

Glad to see I’m not the only one absolutely bemused by how ubiquitous Eclipse seems to be. I avoided using an IDE for many years after a poor experience with a very early version of NetBeans. I stuck with a simple text editor and command line tools like Ant until 2009, when I tried NetBeans again as I needed automated refactoring to make me more productive. Seriously impressed with how it had improved, and with how it easily integrated with existing build tools like Ant and Maven.

Then I changed jobs and was forced to use Eclipse since my new employer had some plugins they’d developed themselves. Oh dear. Eclipse would freeze, require regular restarts, get out of synch with the code, display bogus code errors, mysteriously change or lose project settings. That was not to do with the in house plugins, this was core Eclipse functionality. Then there’s the schizophrenic build system that insists on doing things the Eclipse way, meaning you’re never sure whether it’s rebuilt things or picked up Maven changes, necessitating a time consuming clean and rebuild of everything, just to be sure.

Thankfully I’m now working at another employer where the system is “IDE agnostic” and I can use NetBeans again.

Jose Carlos · August 5, 2014 at 9:00 pm

I work with eclipse since 2003… on those days Eclipse was the better, but now in 2014 its not anymore. Eclipse drains productivity in any java big project, freeze, stucks and have uncompatibility between versions, you must restart your eclipse about one or two times a day, in some cases much more… the problem is Eclipse is obsolete now, the companies must study the problem deeper and understand that a wrong tool can lead to performance lost. The environment in java ee projects are very important and if it not remain stable your team will fail.

Alex · August 11, 2014 at 3:42 pm

Agreed. Eclipse is not the kitchen sink, it is the garbage dump of IDEs.

ArkosX · September 10, 2014 at 6:54 pm

I had to come back here just to scream out of frustration. Once again, out of 8hours of work 2hrs are for the core and 6hrs to solve problems with Eclipse which not only make no sense but there is no information (because proably two people know by heart and they think that is the way to go).
I´m on track to founding my company, I will forbid Eclipse -if possible-.

fhomasp · September 17, 2014 at 9:39 am

This article is very recognizable for me, I’ve been in situations where teammates yell at me at the first time I tell them that an Eclipse feature is poorly working and why IntelliJ does it better. For some reason they can’t seem to look past their usual way of working and ignore the IDE errors, out-of-synch issues, poor Maven integration, … I can go on for hours.
The latest issues I’ve had is a teammate complainting about me for writing a test that doesn’t work. I replied that it works in Maven, and IntelliJ. So for that my nose got bitten off, as he told me that it needs to work in Eclipse. I told him that Eclipse doesn’t make a difference between TEST dependencies and PRODUCTION dependencies, and that he had to play with the dependency management in Eclipse. A showed him what to do and then it works.

Sorry but for an IDE that exists for so long, with plugins for Maven that exist that long, how is it possible that such elementary paradigms are poorly implemented in Eclipse?

Stu M · September 18, 2014 at 11:50 am

I don’t know much about the internals of eclipse or why it does some of the weird things it does, but one thing I can tell you is that everything is a plugin. Eclipse does not to springsource dm server out of the box so whatever it is, it was implemented as a plugin. If it doesn’t work, that’s because the plugin was written badly, blaming eclipse for a bad plugin is a bit silly. Now you have to ask yourself who wrote that plugin, and if I had to guess, it would be somebody associated with the springsource group.

James · October 14, 2014 at 12:39 pm

Eclipse is heavy and cumbersome. The dependencies it implies while building a project goes against every modern software conception (embedded tomcat per default, svn confusing updates, maven dependencies just upgrading for ages without asking). Just the fact that importing or exporting projects takes more than 10 minutes should be a powerful hint enough.
My conception of an IDE only comprises information handling and display, and does not include integrating all possible frameworks and features in one tiny screen hiding an hectic, unmanageable, autarkic giant.

andrei · October 21, 2014 at 4:34 pm

As someone put it: “Reading comments about eclipse is both a psychotherapy for me and a life saver for my (innocent) laptop.”

Why would I otherwise be here, on a 5 year old thread?

Lonely Coder · January 7, 2015 at 1:22 am

As a long time user of Visual Studio (every version since before .NET even), I agree, Eclipse sucks. I have been using it for a few years now, but really can’t stand it. Not just the user experience, there are still some hard bugs in it – e.g. in the properties window, when you are entering a property, and the property gets stuck. Major irritations. Thats why I write this rant, just letting off steam. cheers!

Anonymous · February 2, 2015 at 8:56 am

I can’t stand eclipse. If I’m going to program in Java, I’ll use Netbeans. It is so much more stable & faster.

karlharshman69 · March 2, 2015 at 11:40 pm

In my experience, the only people who really like Eclipse are those who have used it for years. So with each new release, they only have to learn a small amount of new hacks and workarounds.

But I have seen most people who are just starting tend to prefer Visual Studio or even Netbeans because it is so much faster to go from downloading the IDE installation package to productive coding.

Chris · June 1, 2015 at 3:58 am

Eclipse. ..

The user (developer) experience is just horrible. It impossible to find anything (like specific settings) without searching for it on stackoveflow. The menus and dialogs are just hopeless, you look it up on the on the Internet for the first month or so and after that just use memorized click patterns.

There are so many small “features” that just suck (like automatic adding of “)” for methods that cannot be disabled, some weird auto selection of first matching item if autocomplete dialog is open (type “.add(” and you end up with “.addAll(“, like WTF, search settings that make no sense in usual workflow, importing and exporting only keyboard shortcuts is not possible etc.

If you are using more than one tool (realistically a few dozen) they just have to make some sense or you are better off using a simple text editor.

And most importantly everything is slow and you are loosing time with every single click and keystroke. There seems to be small or long delays everywhere. You can even configure the delay for method autocomplete (like WTF). After working with Visual Studio it feels like going back to the 90s.

4 hours after installing IntelliJ I feel more productive with it than with Eclipse that I used for last 6 weeks.

This article just helped me not losing my sanity and smashing something, so thanks for the funny answers, it saved me a few bucks.

Alice · August 12, 2015 at 2:38 am

I love Eclipse. I use it since 2008. I had my troubles sometimes, but yeah, I guess all of you also had troubles with other programs. What to say, I just love it. I can “play” Eclipse through the night, it is so much fun working with it. It feels like writing a book. If there is something eclipse is not able to do, i look for an eclipse plug-in. An in general, there are those plug-ins :) I am writing mostly plug-ins myself, using the build tools of the features and update-sites mostly. I do not like maven, I do use Ant scripts sometimes. But if you write everything as a plug-in, there is no need for maven. The powerful debugger is a luxury, saving me a lot of time! I can understand people saying it is a bit hard to learn at the beginning, but making blog-post to blame a software product? there are a lot of tutorials and help in the web with eclipse and pde, try to learn eclipse. I am still every day impressed how easy some things are done if you are willing to invest a bit of overhead in learning.

just my2cents

ArkosX · August 12, 2015 at 2:49 pm

Alice, it all depends on with what you compare. And having problems… Well there should be no problems out of what you are programming. Imagine you had problems with your hammer every time you want to make a hole to hung something on the wall. In software and particularly with eclipse it is that way. Plug-ins cools, but if you spend more time looking for them and solving the issues with their integration than for the development, again, it is not worth from the perspective of the business. Do you have experience with other ides? Now that Google dropped android to intellij, I think it is a prove that eclipse is not that good. We’ll, as I said months ago here, there was even a study proving the improvements of eclipse when using other ides on top.
Don’t get in love with something just because is what you use.
The whole blog is to create awareness and I found it great. :)

    ArkosX · August 12, 2015 at 2:52 pm

    Sorry about the typos. Predictive keyboard and lack of revision. Received reading my old posts… I DID FOUND MY OWN COMPANY :D

fizalihsan · August 19, 2015 at 12:48 am

I can’t agree with you. I have heard pretty much every response from the first paragraph. I don’t understand how so many developers are still not able to see the advantages in IntelliJ.

In the past 4 years, I worked with 2 different companies where I was the only one using IntelliJ when started. Team mates were so Eclipse-biased, pretty much they say “oh, it is because you are not using Eclipse”. Once I get the things up and running, then I never run into issues with Intellij. After few months, those very team mates came crawling to me, “how is it working for you and not for us”.

Do yourself a favor and starting using Intellij.

Phillip · August 24, 2015 at 9:53 pm

This is a beautiful example of why eclipse is an impossible mountain to climb. For first steps I have got to understand the intricacies of what the difference between an “e4 application” and an “e4 Application Project” is. Then I have to understand what this particular meaning of a “template” and a “product definition is”. Please, for “The first step” you need to get real and understand where your audience is coming from.
The first step

After installing Eclipse 4 the easiest way to get started is to use the e4 template to create a new e4 application. To create a project, choose the „e4 Application Project“ entry within the „new Project“ wizard. For this application you don’t have to change anything except the name of the application. The template creates a product definition and you can start the application simply by starting this product. To start it, open the *.product file and click on run or debug in the upper right corner of the editor. As you can see below, the generated template application already contains a window, two menus, a toolbar and a perspective stack.

Exporting An Android Project From Eclipse Into Android Studio 0.4.0 : Rex St John · January 2, 2014 at 9:26 pm

[…] Eclipse IDE. Remember the good times? So few, so…far between. The time has come to get comfortable with Android Studio, this guide will show you how to pack […]

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.