Now that most major distros only support systemd, other alternatives get less attention, bug fixes, features, etc. So in someways this is seen as a harm to the overall ecosystem.
Comments
Log in with your Bluesky account to leave a comment
There's also an edge case where systemd's binary logging system might make troubleshooting difficult. If systemd breaks somehow, you might not be able to use systemd's journald to read the logs, or logs might never be created in the first place.
This could be avoided if they switched to text logs.
I think there are probably people who are stuck using certain parts of systemd they don't want to use. The fundamental issue at play here is that systemd isn't just one component. It's a whole tool box.
Think of it like this: systemd isn't like mayo. It's more like a blend of 7 herbs and species. If you just want 4 spices from systemd, and replace 3 you can't do that. You get all 7 or none at all. If you chose none, finding good alternatives for some of the spices will be hard or even impossible.
Comments
This could be avoided if they switched to text logs.
Is anyone using systemd because they have no way to use anything else?
http://0pointer.de/blog/projects/the-biggest-myths.html
Where all the systemd haters at? Maybe I just exaggerated those few folks and their loud opinions.
So people want to focus efforts on a modular systemd to reap the benefits of the concerted effort? That's not insane.
But the core value of open source is: don't bitch, just fork.
I hear lots of the former, none of the latter.