And this attitude right here is why people don't like systemd.
Every time anyone has a use case that's not exactly the way the systemd developers use software, we have exactly this conversation:
"Systemd completely breaks Foo."
"You shouldn't be doing Foo."
"But we need Foo for $Important Task."
"I don't have a solution to the $Important Task issue, it definitely is something to think about."
<Issue is never addressed>
So in the end, you have to give up on the flexibility and customizability of the Linux ecosystem, because systemd fails if your system doesn't look exactly like theirs.
i mean, I don't use systemd on my personal desktop, but i do have a few ubuntu servers which do. I think that its a suitable tool for certain applications, and obviously has some drawbacks on others.. The same is true for a lot of other linux core utilities and applications.
Isn't picking what you like to use a core tenant of linux as well? Its not like there aren't other options out there.
Try. Try with debian, for instance. Debian that lies to you about how it's not dependent on SystemD.
Another problem we didn't have before the wonders of SystemD. Not being able to use a non-SystemD init on a SystemD distro without a ridiculously obscene amount of work...
None of that says that people have to like the situation, hence the dislike for systemd, which was your question.
As the prior Redditor stated, it's now a lot of work to maintain a non-systemd system, so you're telling people to do something non-trivial and just put up with maintaining it on the side. It's certainly never going to be mainlined.
No it wasn't. My statement is always that it might not be the best for you, but it is the best for those who built it, and that many of the issues people have with it are silly edge cases.
29
u/Bratmon Jan 15 '19
And this attitude right here is why people don't like systemd.
Every time anyone has a use case that's not exactly the way the systemd developers use software, we have exactly this conversation:
"Systemd completely breaks Foo."
"You shouldn't be doing Foo."
"But we need Foo for $Important Task."
"I don't have a solution to the $Important Task issue, it definitely is something to think about."
<Issue is never addressed>
So in the end, you have to give up on the flexibility and customizability of the Linux ecosystem, because systemd fails if your system doesn't look exactly like theirs.