SoylentNews is people
SoylentNews
Debian Jesse is going to have Gnome3 as the default desktop.
The desktop re-qualification page, used to help choose which desktop will be default, has in the Jesse version a weight for systemd integration, and of course only Gnome3 does it (at least for now). This will surely make the systemd/gnome3 fanbase happy, but possibly will make others unhappy, as it [may] be seen as another step towards mono-culture, until we soon end up with all distros being redhat clones.
This discussion has been archived.
No new comments can be posted.
Integration with systemd Making Gnome3 the Default Debian Desktop
|
Log In/Create an Account
| Top
| 135 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
You are the only person to ever get this message.
(Score: 2) by tonyPick on Wednesday September 24 2014, @11:14AM
Fair point, although it's easier to forgive the odd moment of muppetry if you're actually making something better, versus something which is "less good, just different". At which point everybody else is much more insulated from the level of original delivery.
So I might put up with the crap-in-your-face for the odd diamond, at which point somebody else might be prepared to pick up my "crap filtered" stream of diamonds, and so on. But nobody is going to pile through this for nuggets of yet more crap, and that leads to the problem that all you have is the core group and not much else. (Have I strained that comparison to breaking point yet?).
Likewise if systemd was a well designed init replacement then most folks wouldn't be even hearing about this - it'd be like the device node to devfs to udevd moves, or the procfs/sysfs/sysctl migrations, or any one of a hundred other technical changes that have run through into wider distribution and "just got done".
To put it another way: both Theo de Raadt and Richard Stallman have managed to mightily piss off whole sections of the human race on occasion, and each other pretty regularly, yet they both produce software that people want to use, and have generated communities around that which means you can ignore their....quirks. Mostly. Something that the systemd guys seem to be failing spectacularly to do on any scale...
(Score: 3, Interesting) by Marand on Wednesday September 24 2014, @11:42AM
Probably. As far as analogies go, it was a rather shitty one to begin with. (don't hit me)
Funny that you mention udev, since it (and its creator) are unfortunately tied into this as well, which is part of the problem. I'm not sure if Sievers just happened to make something useful by mistake, or if he got infected later by Poettering's brand of development while working on systemd.
At least you can shut udev off and go back to manually created device nodes in an emergency and still have most things still work just fine. Or you could before it got tied with systemd -- haven't had a need to kill udev since that change. It's getting very difficult to avoid systemd in the same way.