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 most distros are maintained by volunteers except for internet servers and basic system utilities. as the developer of a package like plex, you can reach a much broader audience with something like flatpack or whatever.
personally, i’ve taken to building my own custom docker images for more and more of the software i use, i blow a bunch of my systems away frequently and i get nice isolation. if i want to use something that only works with a newer or older ubuntu, i can!