Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 13 submissions in the queue.
posted by n1 on Sunday September 28 2014, @06:27AM   Printer-friendly
from the yet-another-systemd-story dept.

Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.

Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Monday September 29 2014, @04:37PM

    by Anonymous Coward on Monday September 29 2014, @04:37PM (#99662)

    So you don't accidentally hose all your layer/undo information!

    I actually did that on a project years ago. Thankfully it turned out I still have a previous copy in xcf format, but as far as idiot proofing goes, it isn't a bad idea.

    On the other hand gtk-3 got me to drop everything gtk/gnome related until my desktops had 3d acceleration. GTK-3 is easily 3x or more slower than gtk 2 on non-composite capable hardware. I have no idea why, or if it has been remedied, but I've stuck to gtk2 or qt apps for everything now. And honestly given QT being under the LGPL for the past 3+ revisions I see no reason to use gtk2 if you're writing a C++ app, and if you're writing a pure c app, there's far far better alternatives than gtk3+glib that are far more likely to provide future compatibility and far fewer compatibility headaches.