@TCB13@petsoi It seems to me that systemd is going the exact opposite of the original Unix philosophy of make a tool for a specific task, make it do it’s task well, and then use the necessary tools for the job, systemd is becoming one big piece of bloatware that gets in the way of use rather than helps it.
I don’t disagree with you but… it also provides a cohesive ecosystem of tools to manage linux. What we had before was a poorly integrated mess of smaller tools that was just too hard to maintain and sometimes use.
Besides not all systemd components come out of the box with the base binary, some have to be installed if you need them. And no, it doesn’t get in the way. :)
@TCB13 Problem is by being one big bloatware, rather than a set of small discrete tools, if one part of it misbehaves, your entire system is toast instead of just removing, replacing, or fixing that one part. That’s why that philosophy belongs in Windows NOT Linux.
@TCB13 @petsoi It seems to me that systemd is going the exact opposite of the original Unix philosophy of make a tool for a specific task, make it do it’s task well, and then use the necessary tools for the job, systemd is becoming one big piece of bloatware that gets in the way of use rather than helps it.
I don’t disagree with you but… it also provides a cohesive ecosystem of tools to manage linux. What we had before was a poorly integrated mess of smaller tools that was just too hard to maintain and sometimes use.
Besides not all systemd components come out of the box with the base binary, some have to be installed if you need them. And no, it doesn’t get in the way. :)
@TCB13 Problem is by being one big bloatware, rather than a set of small discrete tools, if one part of it misbehaves, your entire system is toast instead of just removing, replacing, or fixing that one part. That’s why that philosophy belongs in Windows NOT Linux.