3 ms·
Simpler for simple things, which is great when it works, but more complicated for more complicated work, which is simply unacceptable when it prevents you from
by Data_Junkie 7y ago
Simpler for simple things, which is great when it works, but more complicated for more complicated work, which is simply unacceptable when it prevents you from controlling the system. Good old bad design that matters more as you scale up. It isn't the point of systemd that is the problem, it is this particular case of horrible design.
- ses1984 7y agoCan you give an example of something more complicated in systemd? If I ever had to do anything like that, I would just do it in a different layer, like have a simple systemd unit pointing to a complicated init script that contains the logic.
- Data_Junkie 7y agoWell yeah, you would have to. Might as well use initv then. That's the point. At least then you can debug and not have a black box you can't really see into. It is horrid design. Hacker News is getting worse, same thing horrid design . Horrid design is caused by the goals and abilities of the designer clashing with the goals and abilities of the user, and when designers are selfish and want ALL the control the product if useful to less and less people over time. Happens a lot because often the design goal is a hidden desire to wall off functionality to reserve it's usefulness to a select group deemed worthy.
- ses1984 7y agoExcept when would you have to? Please describe something you did that was complicated and hard to debug in systemd.