3 ms·
The sad part is that much of the "standard" is not really standard, but what systemd thinks is "standard". Or that they cling to "standard on paper" rather tha
by digi_owl 9y ago
The sad part is that much of the "standard" is not really standard, but what systemd thinks is "standard".
Or that they cling to "standard on paper" rather than "standard in use", and thus end up rolling back decades of real life usage in the process.
With systemd, perfect very much is the enemy of good. And both unix and Linux go where it is not by being perfect but by being good.
- dozzie 9y ago> The sad part is that much of the "standard" is not really standard, but what systemd thinks is "standard". I didn't mean "standard" as in "POSIX 1003.1e", "SUSv3", or "RFC 3549", I meant it as in "whatever is currently most widely in use". Which actually reinforces your point.