3 ms·

Mostly because the many projects under the systemd umbrella are somewhat coupled and not that easy to use outside of it. For example many of the larger DEs use

Mostly because the many projects under the systemd umbrella are somewhat coupled and not that easy to use outside of it. For example many of the larger DEs use logind because it is good at what it does and consolekit at that time was not really active anymore. That meant that for example freebsd had to either make the DEs work with consolekit (and maintain it) or make a logind implementation work with their implementation. This is one of the confusing things about the discussion. The systemd project very much follows the "unix way" in that there are lots of subprojects that do one thing well, but is developed in a cathedral style (just like the *BSDs are) and not easily reusable, which kinda loses the benefit.

bkor 7y ago
> many of the larger DEs use logind because it is good at what it does and consolekit at that time was not really active anymore. More that ConsoleKit developers and logind/systemd overlapped. For GNOME, logind seemed better and used to be separate. A warning that it would not always stay decoupled was underestimated/ignored. Once logind was tied to systemd all hell broke loose :-P Having something like systemd is great; e.g. GNOME has various user services running. Nowadays systemd manages those user services. But as great as that is, it makes non-Linux more difficult. IMO systemd on Linux makes things very easy and it's better to standardize on it.