3 ms·
I can't speak for everyone, but I switched my website and local PCs over to FreeBSD. In my case, after having suffered through years of broken audio from Lennar
by byuu 12y ago
I can't speak for everyone, but I switched my website and local PCs over to FreeBSD. In my case, after having suffered through years of broken audio from Lennart Poettering's previous grand experiment (and his attitude toward detractors ...), systemd wasn't the only reason -- it was just the bowling ball that broke the camel's back.
I haven't actually used systemd, and I'm sure it runs just fine for most desktop people who don't care how their system boots. But I disagree with nearly all of its design decisions. I strongly value software portability between Linux and BSDs regardless of which OS I am using, I don't believe in making desktop environments like Gnome 3 (and even desktop applications like Brasero) dependent upon a specific init system, I don't believe in monolithic design and prefer stronger decoupling, I prefer text log files to binary log files, I find the documentation on systemd and its APIs appalingly sparse, I am opposed to the heavy-handedness of consuming other libraries like udev, I am greatly opposed to the politics being played out to push its adoption on other distros, on and on.
- stephen_g 12y agoI've actually found Systemd really great for servers. Writing unit files to start our web apps has been so much easier than the old scripts...