Comment Re:Oh no (Score 1) 154
I hate systemd because when it breaks, it generally just stops boot without any diagnostics. It used to take nothing more than a fstab entry that it didn't like (which worked with non-systemd boots) to cause this problem.
I put up with systemd because the old SysV script boot was a horrible brittle mess that would also fall over first chance it got. It desperately needed replacement. It was debuggable but very slow.
Today the lack of diagnostics from systemd is much less of a problem because it very rarely breaks. Perhaps systemd-bsod will finally give decent diagnostics? Although it sounds like it only works for kernel errors.
Either way, systemd haters like me could have written a replacement. We didn't, and the old ways just weren't good enough. We can grumble all we want, those who do the work get to decide which work is done. systemd today is a huge step forward for Linux by every relevant measure and until someone writes something better, this is what we have.
There are a lot of similarities to the PulseAudio project, which was also a mess which got better over time, but unlike systemd never really got good enough. Then someone (thank you Wim Taymans!) actually put in the work to make a great replacement, taking the best ideas from PulseAudio and implementing them better. Perhaps it will happen to systemd as well.
One thing is for sure, grumbling does not help. Only working code helps. systemd has working code 99.9% of the time.