Except, defaults matter. If you ship something that violates decades of well-known behavior, it is at least very unfair (and probably a lot of other unpleasant

Except, defaults matter. If you ship something that violates decades of well-known behavior, it is at least very unfair (and probably a lot of other unpleasant adjectives) to expect downstream to enable the —suck-less flag to restore the expected behavior. The friendly and not bull-headed thing to have done was to ship the new behavior, but enable the compatibility flag by default, rather than expect other people to clean up after systemd's messes. This mentality is the main reason bag on systemd all the time. If systemd does something to annoy you, it is automatically your fault for doing something Wrong or not enabling some obscure config file option. It's never systemd's fault when systemd unilaterally violates the principle of least surprise.