@alrs @solderpunk Hm, I guess I don’t mind that much, as a end user. I was never all that invested in the details of what they’re using, I just liked how apt mostly always worked. And I want to use the same OS on the server and on the laptop. If I want to get back to a world I understand I imagine myself going back to Slackware. (It focuses on KDE I guess?)
@kensanata @alrs My main complaints are: ridiculous plurality of packaging tools (do I use apt-get or apt-cache or aptitude or dpkg to do X?), ridiculous splitting of packages (foo, foo-config, foo-doc), over-zealous designation of packages as "required" or "recommended" leading to bloat being pulled in, substantial modifications to upstream software (e.g. splitting up config file sections into separate files) and, yeah, systemd.
I have considered Slackware, but from what I understand the dominant philosophy there is "just install the entire standard system", and I strongly prefer a minimal base install and installing only what I need via a good (simple!) package manager.
Recently I played with Alpine linux in a VM (somewhat ironic, as I have no interest in containers, which seems to be its main niche) and kind of liked what I saw. I might be a tad too minimalistic for a typical desktop, but TBH I am thinking of giving up on that notion and doubling down on the minimalist retrogrouch thing.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!