[dozzie]

This "pile bash scripts with sleep n" was at least debuggable and could be inspected and traced in different ways. With systemd, when something doesn't work as expected (which is often when you do anything that deviates even a little from standard), tough luck.

[digi_owl]

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]

> 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.