I've been using Alpine recently on my X200, and while it does require an arch linux chroot for some applications (due to some slight musllibc/gnulibc interop pr

I've been using Alpine recently on my X200, and while it does require an arch linux chroot for some applications (due to some slight musllibc/gnulibc interop problems), overall it's one of the most pleasant, and stable distributions I've ever worked with. As a regular user of systemd (I use arch linux as my main and therefore was one of the first adopters of systemd) I am subjected to irregular and weird irreplicable bootup bugs and timing problems. Alpine reminds me of a simpler time when my computer's bootup was deterministic, and a hang at boot was only ever caused by a disk problem, rather than something trivial like having to wait 3 minutes because it can't connect to the network. I totally understand the reason for there to be 'bloat' in projects like systemd, GNU libc, etc. And I understand that often that bloat is needed, to cover the edge cases in the thousands of use cases for which they are deployed. However, it's only really when I moved to Alpine that I understood just how much of it there was, and how much of an impact it had on not only my interactions with the computer, but other concerns like my energy usage, etc. It was a like a breath of fresh air for me, and it reminded me that computing could be good, again.