i like gentoo
not just the os but the community
it's mostly older guys but it couldn't be further from the techbro circlejerk these spaces usually turn into
the philosophy of the os is every configuration is encouraged and supported no matter how much it deviates from defaults or from the mainstream
this translates into how humans are treated
gentoo people actually genuinely care, about ethics, about diversity, about people's niche use cases, many of them use older hardware and make sure it stays supported, there's a class aspect to that too you know
@lizzy How is Gentoo these days? I used to run it on a few PCs maybe 15 years ago, even was a "developer" and maintained a few small packages for a while, but as I had less and less free time, I gradually moved to Debian.
@ticho i would say it is still more time consuming than most other distros, yea
@ticho however, thanks to the binhost, there is less of a time burden when it comes to compiling
@lizzy I remember I loved their etc-update utility to merge the config file changes. Am missing it to this day on Debian, as well as on corporate distros at work.
@ticho @[email protected] i think that tool has been replaced by dispatch-conf? which just calls diff (or whatever your diff tool is set to.)
@ticho @[email protected] either that or im dumb and you were just saying what dispatch-conf does and not that it was literally etc-update before

@puppygirlhornypost2 @lizzy Yes, they were phasing etc-update out even back when I was still there, but for some reason I liked it more than dispatch-conf.

They were (at least at the time) functionally pretty similar, I think - they'd iterate over unprocessed config files, letting you keep old or new version, or merge them interactively, hunk by hunk. Or launch $EDITOR to do whatever you want.

@puppygirlhornypost2 @lizzy That interactive merge was the thing I miss. Often you'd only tweak a line or two in a given config file, and this allowed you to comfortably go through any proposed changes in the config file, which often were just typo fixes in comments, or newly added options. Diffing and going hunk by hunk laid it all out very clearly.
@ticho @[email protected] yeah it's way better than when a distro just does a system update and is like "all your config files are located where they were but with .old at the end good luck" (best case) or worst case they just up and fucking delete your config (Where the fuck is my /etc/pipewire/pipewire-pulse.conf fedora?)

@puppygirlhornypost2 @lizzy Yeah. Although RedHat, Suse and Debian at least install most of the new configs as .rpmnew, so your old, working configs are still used, but you still have to inspect them yourself, without anything helping you.

And vast majority of server owners at my work either are not aware of this, or ignore it out of laziness. We've had unnecessary outages thanks to that! But I digress.