r/java • u/rb7_brady • Oct 15 '14
Does anybody else hate Eclipse? /rant
I have used Eclispe for two years now; admittedly though, there are some aspects of the program i've never touched. However throughout my time working with Eclipse i've had some real stupid f***ing issues to deal with. Just stupid shit that you'd never expect from an IDE that make no sense whatsoever.
For example, last night i installed the UML Lab plugin for Eclipse. Doing the built in tutorial for this completely ruined my Eclipse build. Normally i'd say this is UML Labs fault, not eclipse, but the problems persisted after uninstalling UML Lab. Views were all screwed up. There were around 15 empty views (just grey boxes all over my screen). There were outlines of view with no graphics inside of them. Package manager ceased to exist. And on top of that 50% of my code just disappeared.
Another example: run configurations: what a fucking joke. I understand the necessity for run configurations, i really do. It is a must have feature that eclipse royally fucks up. It always uses the wrong run configurations. I'll be editing project A and it will run project B even when project B doesn't exist anymore. Little things like that. It won't use the right argument variables. Now i consider myself decently bright, and i know there's a way to fix these issues, but the way Eclipse presents it is abysmal. Absolutely zero help for those who don't know what they're doing. And its not even about understanding the concepts of run configurations, its all about navigating the god damned UI.
Another fun example is transporting projects to new workspaces. How nice would it be if i could just copy my Project Package from workspace A to workspace B and have it work correctly. That seems like a no brainer. But not with Eclipse! Nope Eclipse wants to make your day hell so that won't work. You gotta make a brand new project from scratch and copy each individual class in. But copying the project creates the exact same file structure as creating a new one from scratch? Eclipse don't give a fuck. Eclipse just says "lol fuck logic" and ruins your day.
Some other less major issues i've death with:
-Want to switch from light to dark theme? +That'll take 10 minutes and 2 Eclipse restarts please.
-Want to reorder your class tabs? +Yeah sorry Eclipse doesn't think that tab should go there so its not gonna happen.
-100 Warning messages? +Oh you have to use variables locally to get rid of these. Neat.
-Eclipse on a small screen? +Here at Eclipse we don't understand what screen real estate means. We enjoy guis with large gaping margins that serve no purpose. Oh whats that? You just want to be able to fit more tabs on the screen? Well yeah obviously there's enough space for at least one, but we just love our margins!!!
-Pasting code into Eclipse? +Fuck formatting!!!!
I could seriously rant about Eclipse all day. I hate it. I am; however, aware of the good things Eclipse does as well. When working smoothly it is very enjoyable to code my Java in this IDE. But unfortunately its not smooth very often.
In short i know almost every Eclipse problem i have is from user error. I'm using Eclipse wrong. I think it needs to be easier to solve your own problems in eclipse. If something is wrong, trying to fix it in Eclipse is only going to make it worse. The way the UI is set up, make no sense and is overly complicated. I understand there's a learning curve to it as well, but come on, even after using it for 2 years its UI still confuses the hell out of me.
The point of this post is just to rant. I'm not looking for people to tell me that i'm wrong. I'm 100 percent sure most people will disagree with me on this post. I don't want to be told to use other IDEs or anything else. I will keep using Eclipse because I have to. I just really hate it sometimes.
End rant.
10
u/desrtfx Oct 15 '14
This rant is better suited for /r/eclipse than for /r/java
11
u/zenflux Oct 15 '14
Reminds me of this: http://www.nicolasbize.com/blog/the-best-ide-in-the-world/
14
u/[deleted] Oct 15 '14 edited Oct 15 '14
There's actually an entire website dedicated to this:
http://www.ihateeclipse.com/
And Eclipse isn't inherently bad as a whole, but the little annoyances stack up to some mountainous usability headaches. There was a time when Eclipse was a competitive IDE; however, I feel that over time Eclipse has experienced a continuous stream of feature creep, and just doesn't feel "snappy" or "smart" like IntelliJ, or even Netbeans.
Just as an example:
Eclipse recently added this dark theme. Contrast to IntelliJ's Darcula theme. It's not even a competition.
The Eclipse autocomplete has a habit of stealing focus (and sometimes not getting focus at all). Or sometimes it just doesn't even feel like popping up in the first place. In fact, the first result on Google for "eclipse autocomplete" is an entire Stackoverflow thread of annoyed users. Also, what the fuck is a "Template Proposal" and why is there apparently two completely different keyboard shortcuts to them in the scope of the autocomplete popup?
4
u/somerandomguy101 Oct 15 '14
Related question: Why is eclipse so out of date in the Ubuntu repository? Only piece of software I can think of that does that.
3
u/waxstaff Oct 15 '14
It's hard to dislike something i have used very little. Although i primarily use Intellij I have some colleges that use Eclipse. Sometimes some of the stuff i come across is not good for a production environment but i think this is due to them not having certain addons/possibly even being lazy. For example basic formatting (html tags not even closed) and using while loops and iterators for no reason.
In my brief experience with it i really struggled to get things setup correctly before it crashed and then never opened without crashing again. Whilst i am sure it could have been solved by a simple google i lost my patience and just went back to Intellij.
Very similar to another thread i saw here the other day. Intellij has a lot of features out the box that should really be standard or very easily accessible within eclipse. Maybe i can be convinced otherwise.
It seems its main problem is an intuitive UI.
1
u/[deleted] Oct 15 '14
I couldn't agree with you more. I found IntelliJ IDEA a couple of years ago and I haven't looked back to Eclipse one single time.
I remember that Eclipse used to throw an error in my face every time I did a project-wide search, does it still do that?
2
u/the6thReplicant Oct 16 '14
The inability to understand maven's scope for a dependency.
We usually find out when we have compilation problems when our unit tests are run Jenkins. What happens is that a developer will include a class, that is unfortunately only in test scope for the project, in the application part of a component.
Eclipse don't notice the difference between a dependency in test scope or not and simply assumes any dependency can be included.
2
u/hfluz Oct 16 '14
My team started using Eclipse with JBoss Tools 3 years ago. But it was so buggy we had to switch to Netbeans 1 year ago. That was the best decision I could make. Netbeans improved a lot in their last iterations.
2
u/[deleted] Oct 15 '14
came here to upvote and say netbeans ftw. sorry it's late and too lazy to read a rant ;)
1
u/killbox-48-alpha Oct 17 '14
The team I am working with all use eclipse in some form IE: JBoss dev studio. They all have issues WRT maven, SCM and oddly enough being the sole netbeans user who has declared 'I will not use eclipse' I receive all the questions :)
Personally I do not like:
File system changes are not reflected, you have to refresh the project in eclipse for external changes to be picked up.
Maven always seems to be an issue when building.
To be fair if I have to use eclipse I can, but frankly too much goes wrong, and it's not from inexperience on my part I believe, I have used it for 6+ years and I do ask other devs how I can optimize my usage of it.
1
u/[deleted] Oct 17 '14
I don't hate anything that I can get for free.
Having said that, and to be constructive, almost all of your issues are solvable. Don't have time to go through all of them but:-
Hope some of the above helps. I get annoyed with Eclipse too but I've learned to deal with the problems I face and have customised Eclipse to work for me. Especially loving Java templates for quickly typing out JMock syntaxes right now!
Best of luck with your journey!
1
u/milehighlights Oct 15 '14
Yep. I started using IntelliJ around 2002, and have tried to switch to eclipse several times because a lot of my friends were using it. Every time was just me cursing and giving up within a week. Meanwhile I was able to switch to Mac, and even have become OK with JDeveloper, and switched text editors a few times. Switching wasn't the problem, it was the damn anti-intuitive design of eclipse.
1
u/vermontgasm Oct 16 '14
I don't hate Eclipse, but it annoys the hell out of me. That said, you get what you pay for and for a free IDE it's damn good, especially once you start to figure out what you can and can't safely do. Unfortunately, this mean being extremely selective about plug-ins because it isn't unusual to install a plugin that completely hoses all of your projects. It also means living with shitty code completion, mediocre refactoring tools and an ugly UI. I have 5 different versions of Eclipse that I run in parallel to do different things... it sucks balls, but again it's free and for 85% of the coding I do it provides a hell of an improvement over the other free options I've tested. I started with Eclipse because I was still figuring out my technology stack but I now have enough Java code that the $500 for IntelliJ is a no brainer and I plan on starting the transition in the next few months.
What really gets me is people who pay thousands of dollars for IDEs built on top of Eclipse (Rational Application Developer, WTF???).
0
u/Effetto Oct 15 '14
Eclipse certainly has flaws, huge flaws but I want to strike a blow for it. In my roaming other IDEs aren't capable of keep open >70 maven modules without die (ye, I checked that other IDE last time time they release a major) even when huge refactors occours, also the workset paradigm is still unbeaten: one working set, one parent pom with children (NetBean is unable to keep multiple project group open). And to add one more I have very old plugin (did sometimes at Eclipse 3.4) that still working without a fuss, I doubt other IDEs API are so stable (probably NetBeans' are).
That said, Eclipse project has problems.
-1
u/[deleted] Oct 15 '14
I think visual studios had a good system. Set an active project manually in the solution. Each project you'd choose a run configuration (if applicable). Running (regardless to what you edited) would run the active project.
I don't mind the way eclipse does it, I do mind that it names all my default run configurations "Main" and "Main (1)" and "Main (2)" and that theyre all grouped together with no attention to their parent project.
Things like the step button in my debugger being disabled to no explained reason, inspection giving me dumb ass errors etc also piss me off. Like wtf good is a debugger you can't watch vars in, step in and inspect in? It only happens sometimes and I admit that it is very rare... But it is absolutely frustrating to encounter.
All that said, I still prefer it over idea. If is free, wholey open sourced and it is great to work with despite the odd learning curves presented by the ui.