On Linux and conflating the tool with the work of the tool.
https://media.sully.site/the-tool-as-the-work/ #linux

@sullybiker i am just absolutely in love with the fact that you categorize slackware as a “mid-2000s” thing, never change. ;d i associate it with like, 1993 and floppy disks. wikipedia says, and i think this is true, that the “slack” is regarding the maintainer’s effort toward the distro. he still does just random releases to this day, has no bug tracker or central source repo.

@sullybiker jokes aside tho i’m glad to see folks newer to the game running the gamut. slackware is most like BSD IIRC, you can get some binary software, but generally are encouraged to compile everything from source. there is an understanding of the system and confidence in what you have that comes from that.

@justizin I've found snaps and Flatpak have made me very lazy, so I try to avoid them now, as much as I can.

@sullybiker i’m fine with being lazy, i think when you want to get things done, its great to get things done. my team supports the base images for probably a couplefew hundred containers at work, some build environments, etc…

i’m probably better at supporting ubuntu and alpine bc of the time i have spent hand crafting bespoke OS installs.

@sullybiker Linux From Scratch was an *incredible* resource, I also havent touched that in decades, but it seems to still be chuggin along.

@sullybiker compiling your linker from source will really get the ol bones shakin ;)

@justizin KISS is cool too, I liked the clear-headed philosophy behind it.

@sullybiker just like, the unix philosophy KISS, or something specifically slackwarey?

@justizin I had a lot of fun with it, but lost a lot of time screwing about with the kernel config because Kiss encourages everything in kernel (no initramfs although it's optional) and it's a job to get the storage stack behaving