4 ms·
> systemd isn't and shouldn't be a requirement for applications going forward. Any application that requires it is limiting its portability for unknown reasons.
by Bromskloss 10y ago
> systemd isn't and shouldn't be a requirement for applications going forward. Any application that requires it is limiting its portability for unknown reasons.
How should one do it instead? Treat each alternative system specifically? Or is there a way to cover them all at once, including unknown and future ones?
- groovy2shoes 10y agoHow about this: don't write applications that depend on the init system. Seriously, who ever thought such a dependency was a good idea? Who even thought it would be a good idea to make an init system that was possible for an application to be dependent on? This is exceedingly poor engineering, and I'm dumbfounded at its acceptance and spread.
- qmr 10y agoHint: Programming is not engineering.
- groovy2shoes 10y agoI've heard this before, but I've seen pretty convincing arguments both pro and contra. I'd actually love to discuss this (not argue -- I honestly don't have a strong opinion on the topic at this time). If you're willing, my e-mail address is on my profile :)