While I don't enjoy the fact that this introduces a ton of maintenance issues on systemd-less systems that would like to continue supporting GNOME, I do think leveraging systemd to elegantly revive the session save/restore functionality bodes a lot of optimism for the set of features that will follow.
I'm at least thankful that this maintainer/contributor dedicated about half of their announcement on how systemd-less systems could alleviate this issue.
Well this is bound to be controversial, to say the least. GNOME and systemd are two pieces of software that attract very polarized opinions.
I'm interested to see how this evolves. The planned session restore feature sounds nice. With the Wayland changes coming too, GNOME 50 should be a big deal, one way or another.
Ubuntu + Snap + GNOME + Wayland + Systemd
Holy moly, there is a lot of stuff for haters to talk about. Each of these parts are very polarizing on its own, but combined, phew.
You forgot rust 🦀
There are only 2 types of people. Who hate systemd and those who don't know what systemd is. \s
I think for those people it boils down to systemd being an init system that does more than an init system maybe should. Combine that with it being more complicated to work with and with Redhat not really being that open to feedback.
It is another word for patriarchy, right?
Maybe it's not so great how monolithic systemd is, but it has brought a lot of great functionality to the Linux world. Not as if Linux has ever been married to the Unix philosophy anyways.
While I don't enjoy the fact that this introduces a ton of maintenance issues on systemd-less systems that would like to continue supporting GNOME, I do think leveraging systemd to elegantly revive the session save/restore functionality bodes a lot of optimism for the set of features that will follow.
I'm at least thankful that this maintainer/contributor dedicated about half of their announcement on how systemd-less systems could alleviate this issue.