You can also read The problem with the anti systemd attitude.
This is not just hatred towards systemd, it can do things very well, the direction it is going isn’t great.
You can also read The problem with the anti systemd attitude.
This is not just hatred towards systemd, it can do things very well, the direction it is going isn’t great.
“Soldier Found Deep In Jungle, Still Fighting For Extinct Empire!”
This guy was complaining in the blog post about how bloated systemd is because it uses 36MB of space and it could be done with ~6MB if you used different tooling.
If you’re the kind of user where 30MB of disk space genuinely matters either at scale or in some very niche edge case, then you’re also the kind of user who won’t have much trouble using an alternative init system or building/tuning your own.
Okay, I agree 30MB isn’t a big deal, but that’s not really an argument not to optimize. The entire Debian Stable mirror for example has like 70,000 packages in it. Let’s say all of those packages took the position that “A few extra MB doesn’t matter.” If each one had just 1 extra MB that is 70GB of extra bloat. If each one had 2 extra MB that is 140GB of extra bloat. If each one had 30MB of extra bloat that is 2.1TB of extra bloat. Now obviously thats a very unrealistic, and extreme, example, but the point is that with a super complex operating system things add up. We should appreciate the nit picky little dudes who yell over 30MB because they’re probably responsible in part for a good bit of cumulative extra disk space for the rest of us.