SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
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.
Always do right. This will gratify some people and astonish the rest.
-- Mark Twain
(Score: 2) by Bot on Wednesday September 24 2014, @06:37PM
Account abandoned.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @07:35PM
And that's worse because ...
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @07:39PM
Or a yessir to RedHat.
Thanks Debian & Ubuntu, for holding the line. Way to really stand up for yourselves.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @07:42PM
Exactly -- there's no real difference here. The "circular logic" post from above pretty much says it all.
If the supposed COMMUNITY got its way this wouldn't be happening. Clearly it doesn't.
Same thing, different CEO.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @07:46PM
Yep, that's what's killed it for me. When Linux was sort of on the edge, the entire character of the 'movement' was different. It seemed like a perfect mix of ideology, brains, and determination.
Now that it's essentially as 'edgy' as your local McDonald's menu (and about as interesting), shit like this is going to continue to drive people into the arms of Windows and the BSDs, which I'm not totally sure is a good thing either.
Such is the way of things, however. Sad, though, to see it end this way.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @07:52PM
Actually you know what? This is even WORSE than a yessir to the CEO of MS or Apple.
Here's the thing: at Apple or MS, the CEO doesn't care about things at the level we're discussing here. Who does care would be the technical team responsible for the part of the system in question. That team presumably would have some sort of a lead who would be the ultimate decision maker as to how things will or won't work, and what will or won't be implemented. And a good lead would of course listen to his or her team.
What we have here is a situation where the entire technical team (in this case more or less the entire community of Linux developers) is saying "no no no this is a terrible idea," and has completely logical, valid, rock-solid reasoning on their side, and they're getting a middle finger as the response.
At MS or Apple unless you have a complete asshole at the technical decision-making level who ignores their team this wouldn't happen, and chances are that sort of person wouldn't last long. And if you do have a complete asshole at the helm, well that's the boat we're in right now with this whole mess.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @08:00PM
(in this case more or less the entire community of Linux developers) is saying "no no no this is a terrible idea," and has completely logical, valid, rock-solid reasoning on their side, and they're getting a middle finger as the response.
B-B-B-B-BUT IF YOU DON'T LIKE IT, FORK IT!
That might've worked at one point, but now that everything and its dog is going to be inextricably bound to System D, you'll be forked all right.
With no reacharound.
(Score: 0) by Anonymous Coward on Sunday September 28 2014, @12:46PM
WTF is "System D"?
If you're clueless enough to call it that, I don't expect you have any idea why it sucks, or how to configure a system that doesn't use it.
Actually, from this whole article I've got the impression that a lot of "nerds" have forgotten how to configure a Linux distro installation.
Anyone who thinks a userland init package has become critical for any and every install is holding it wrong.
RTFM or GTFO!
(Score: 1) by donjan on Thursday September 25 2014, @12:34AM
What we have here is a situation where the entire technical team (in this case more or less the entire community of Linux developers) is saying "no no no this is a terrible idea," and has completely logical, valid, rock-solid reasoning on their side, and they're getting a middle finger as the response.
I'm not a fan of systemd myself, but the quoted statement is false.
What we have is the vast majority of the "technical team" either agreeing with the proposed change or being indifferent to it. On the opposite side, a minority is saying "this is a terrible idea" and backing it up by some solid reasoning, but the problem is that too many of those people are armchair developers who push back for ideological/sentimental reasons like "one-task-per-binary-unix-philosophy", "RedHat-wants-to-dominate-all" and "I-dont-want-to-learn-journalctl-instead-of-using-grep".
While I happen to sympathise with all those reasons (especially the dislike of journalctl) and more importantly with criticism put forth by people like Rich Felker and John Vincent, you and I have to be fair and accept the validity of the pro-systemd reasoning. Which is more or less successful in rebutting technical critique while questioning the necessity of the ideological reasons (either as dogmatic, tinfoil-ish or plain lazy).
And there's the crucial point: we can't prove that systemd with all its advantages and drawbacks is not an improvement to sysvinit, we can only say that we don't like its flavour. But FOSS is the so often lauded do-ocracy, and so far sysvinit, OpenRC, Upstart, runit and others have apparently failed to deliver, which leaves the field to systemd.
(Score: 0) by Anonymous Coward on Thursday September 25 2014, @08:58AM
so far sysvinit, OpenRC, Upstart, runit and others have apparently failed to deliver, which leaves the field to systemd.
False.
"Failed to deliver?" Ha!
System D answers a question that most of us aren't/weren't ever asking. A vocal minority and their toadies waving around B.S. like "This prevents logfile tampering" is a sure admission that this project is a blemish on the face of society.