Mir likewise states that inherent incompatibilities is exactly why they're creating a new project as well. Though a big difference being that Upstart is actuall

Mir likewise states that inherent incompatibilities is exactly why they're creating a new project as well. Though a big difference being that Upstart is actually in use, whereas no one's using Wayland. To be quite honest, a lot Poettering's rationalizations with systemd, especially when discussing other inits like launchd, seem to be purely NIH. He could do this work and organize with what's already out there, but he'd rather do our own thing. Instead of creating a system that is backward compatible, he's saying for daemon writers to write for a completely new specification, and to ignore any pretenses of compatibility, like not double forking. More discouraging are the intentional incompatibilities, and statements that they're only targeting the linux kernel and udev, and will reject patches that make it more compatible with other systems.