4 ms·
Good riddance! Sysvinit shell scripts are a pain to read and maintain. Developers that perpetuate systemd flamewars have gone from mildly entertaining memes to
by rubiquity 3y ago
Good riddance! Sysvinit shell scripts are a pain to read and maintain. Developers that perpetuate systemd flamewars have gone from mildly entertaining memes to being a serious red flag and not anyone I’d ever want to work with. systemd and its ecosystem is proven and always getting better.
- jmclnx 3y ago[flagged]
- Bombinator 3y agoDon't you think it does a bit too much as an init system?
- rubiquity 3y agoIt’s not just an init system and you can opt into resolved, networkd, etc. but you knew that already!
- op00to 3y agoNo, it does what I want well. It never surprised me.
- tekla 3y agoWhat does it do as an init system that is too much?
- tptacek 3y agoNo. It’s great, replacing and unifying a whole collection of random tooling you otherwise had to cobble together yourself.
- diffeomorphism 3y agoNot really, no. Systemd-init seems fairly focused. systemd the project also makes other stuff, which all neatly fits together.
- akerl_ 3y agoJust being able to treat period tasks the same as I treat long-lived services, and never having to think about crontab vs cron.d vs cron.hourly vs /etc/crontab, has improved my quality of life dramatically. I also use systemd-timesyncd / networkd / resolved on most of my systems, but in places where I've wanted to not, swapping them out is as easy as swapping any other services (looking at you, rsyslog and syslog-ng).
- washadjeffmad 3y agoCertainly! It can also be difficult to distinguish between being genuinely liked and politely tolerated because of being "good to have around". I mean init systems, of course.