Gregory's Server@ariadne the polyfills to systemd api (elogind being the major one in linux, which is just systemd-logind extracted out) can't really be fixed by another init system that isn't systemd tho
because what those apis do, are not init management. it's session tracking (logind), it's device management (udev), it's a dbus api, and so on.
what would be needed is good replacement for those parts. consolekit died, seatd[1] is trying, but the major desktop environment got to using systemd's bundled apis for non-init-stuff, and well, while it's doable to make new specs/apis/implementations of those, trying to provide the same api is kind of an impossible task.
more to it, as more and more distros go to systemd, less work would even be put on those (either alternatives, or polyfills), and then, we'd really have no other option but systemd.
1: https://sr.ht/~kennylevinsen/seatd/
because what those apis do, are not init management. it's session tracking (logind), it's device management (udev), it's a dbus api, and so on.
what would be needed is good replacement for those parts. consolekit died, seatd[1] is trying, but the major desktop environment got to using systemd's bundled apis for non-init-stuff, and well, while it's doable to make new specs/apis/implementations of those, trying to provide the same api is kind of an impossible task.
more to it, as more and more distros go to systemd, less work would even be put on those (either alternatives, or polyfills), and then, we'd really have no other option but systemd.
1: https://sr.ht/~kennylevinsen/seatd/