That's the theory yes. But unfortunately with systemd it didn't work out that way.
See, the GNOME developers decided to make systemd a hard dependency, this pretty much means that (binary) distributions that want to keep offering GNOME to their users have two options:
a) patch GNOME to work without systemd
b) switch to systemd
I don't want to run my *desktop* over a network, that's horribly clumsy compared to pulling over only select applications.
Having had to deal with the entire RDP/VLC crap only made me like X11's way of doing things more.
None come with Subversion support, they tout CVS and Git support though, but the reality is that most companies, will still be using Subversion, so the majority of people will have to hunt for at least this plugin (of which there are two competing ones, so you get the joy of figuring out which one to use as well).
The various bundles (there seem to be more every time I check the Eclipse website...) also seem more like a crutch to compensate for how horrible it is to find and install all the plugins one would need. They also seem to cater to some person's idea of what a certain type of developer would need rather than their actual needs, leading to loads of superfluous cruft installed and needed plugins still being missing as for example the JEE package doesn't appear to be a superset of the Java developer one.
Of course one could install a whole bunch of different Eclipse bundles just to have access to all the stuff one needs, judging from the descriptions I would need 2 or 3 Eclipse installs and I would still need to hunt down the Subversion plugin.
Let's just be honest, installing Eclipse and acquiring all the plugins you need is a pain in the neck and always has been (though given that the number of plugins available has gone up one could make the argument that it's become worse). The bundles seem more like an excuse to leave the festering pit of refuse that is Eclipse's plugin management alone instead of fixing it. Both NetBeans and IntelliJ do a much better job in this regard and I wish the Eclipse devs would take a look over the fence for ideas on how it should be done instead of making excuses for something that has been broken for 10 years.
It's still a sluggish bloated memory hog
I wonder how much of that is due to the fact that it's written in Java. Seriously, I don't know but I'm curious. This is not meant as flamebait (though I'm still glad I wore my Nomex undies today).
Java (or the JVM) likes memory, lots of it. But that's not the (only) reason Eclipse is a memory hog as other Java based IDEs (NetBeans and IntelliJ come to mind) manage to do much better on the same system. I'm not even sure that Eclipse uses that much memory compared to the competition, but it sure is more sluggish in use and it hasn't improved in that area in as long as I can remember.
My experience is the same as the AC you replied to, Eclipse pretty much hasn't evolved in a meaningful way (for an end-user, maybe the platform is great to work with, I wouldn't know) since I first used it back in college (iow, 10 years ago) and that is a shame.
Dealing with plugins (and their update centers, oh dear) is still a major pain, it still doesn't support basic features natively (I mean when I last tried it half a year ago there still was no Subversion support in the default install. I mean, really? Hunting down the plugin for it was a pain as well) On top of that Eclipse's maven support is simply atrocious which imho is entirely unacceptable for a modern Java IDE.
The one thing it has (imho) going for it is that Oracle has dropped pretty much all non-Java language support from NetBeans, meaning that if you need proper support for a non-Java JVM language Eclipse is where you go (unless you want to shelve out for IntelliJ or can make do with IntelliJ's free edition). Eclipse is also the platform used for most commercial Java ecosystem plugins, so if you are dependant on some of those you're probably stuck with Eclipse.
I personally went from being an Eclipse user, to a NetBeans user and now I'm using IntelliJ. I still use the other IDEs occasionally, if only to keep up-to-date with their status and be able to support my colleagues with various issues, but until Eclipse actually starts improving in areas that matter (UI, plugin management and a sane default feature set) it's just never going to be my go to-IDE again.
FWIW denying the Holocaust is also illegal here, in Belgium, and I wouldn't be surprised if it were so in many other European countries as well.
Not that it would matter too much if it weren't, there's something about denying the well documented mass murder of various ethnic groups (Jews, gypsies and homosexuals off the top of my head) that tends to make one rather...unpopular... in society. If anything these laws might protect Nazi-sympathizers that would otherwise have been too stupid to keep their mouths shut.
Having tried to deal with Scala's macros I have joined the camp of "it's a seriously worthwhile tradeoff".
Honestly doing anything with reflection in Scala (or pretty much every non-Lisp) is just horrifyingly unintuitive (and as a result: painful). In a Lisp you're just manipulating lists using typical list manipulation functions, it is, comparatively, a piece of cake.
Reading Paul Graham's "Why nerds are unpopular" seems relevant if one wishes to dig deeper into this topic.
Geeks by their very definition have have interests that set them apart from the popular kids. "Geek" and "popular" just don't mix, though one could be popular among fellow geeks, but I'm pretty sure that wasn't what the OP had is mind.
As for GNOME - I realize that GNOME 3 is different from GNOME 2, but I'm at least happy that for once the Open Source community *tried something different* instead of just aping Windows or Mac OS X (though GNOME 3 is obviously inspired by the latter).
The two billion different window managers out there supporting every imaginable workflow would like to have a word with you. Yes, they're still out there, despite all the efforts of the "userfriendliness" crowd to break them.
Maybe it worked, maybe it didn't, but at least we can claim to attempt to lead, instead of just blindly following.
The problem with GNOME isn't whether it sucks (I haven't really used GNOME since the crap that was 2.0, so I have no opinion on how good or bad it is), it's that they have decided that their way is the only way and have taken over independent projects (like GTK, the "G" really doesn't stand for GNOME and it is definitely not only used by GNOME applications) and are forcing their views on those as well.
The FLOSS community used to be about cooperation and choice, but lately it seems to be more about which corporations can hire the most developers to force their vision onto the projects they support without any regard to the rest of the ecosystem.
A computer without COBOL and Fortran is like a piece of chocolate cake without ketchup and mustard.