Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I decided to not act on it, take it easy and roll with defaults. After all alternatives remained, it is an upstream project indeed, etc But I took quite a bit of interest in the discussion as it raged on over the years those arguments you've used I've seen time and time again.

Especially this: "If another open source program depends on it by default, then you can patch it to remove the dependency." and "then it's up to you if you want to use some feature or you want to do it a different way."

Now recently also Debian has decided to drop support for other init systems. It just wasn't practical anymore. Now you get to be on the lookout when you "want to use some feature or you want to do it a different way." because if you don't you end up with shit like this: https://news.ycombinator.com/item?id=19291067 Now we get to see hilarious stuff like a systemd developer asking tmux to add systemd specific code to work around systemd's own default behaviour. Now we get BSD's putting in work to deal with the prevalence of Systemd. Now we get those working with embedded linux putting in work to deal with the prevalence and dependency on SystemD. Because at the end of the day the systemd devs don't care about ulibc, non linux and what have you whilst at the same time seeming to really want to set the standard for as much as possible.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: