@tistan
Świetny komentarz z reddit (akurat tej kwestii na blogu nie poruszyli, dla którego zrobiłem DV):

logind: its basically the same thing. Consolekit is not maintained anymore, but logind was implemented by systemd to take over that job. Also it is a more sane implementation with a lot less security holes and again, it tighs into the systemd infrastructure quite nice. After all, a user session is about handling running processes, managing ressources and devies as well.
Now of course you can complain that you cannot just use logind without systemd, but I think it is totally legit that systemd devs don't want to go through the trouble of maintaining a use case that they do not care about. They did write it as a component of systemd, not as a standalone daemon.
Of couse, you can again complain that this "forces" you to use systemd, if you want logind. But again, it is not systemd's fault that nobody maintains consolekit or implements an alternative. No one stops anybody from doing that. But its not the job of the systemd guys, as they are obviously the ones who already provide that functionality - by using systemd.
This by the way is also an argument for the GNOME people. If consolekit is an unmaintained mess, and there is not other alternative then logind - of couse they should use logind. What else are they supposed to do? Write their one plumbing layer for every piece that is only provided by systemd, so that people who do not want to use systemd but also do not want to provide alternatives are happy? I think not.

Link