• 13 Posts
  • 15 Comments
Joined 2 years ago
Cake day: June 11th, 2023
  • eah@kbin.socialtoLinux@lemmy.ml•Something to ruffle some penguin feathers: The Unix Hater's Handbook
    8·
    11 months ago

    I’ve been reading this for a few weeks now.

    There’s a section talking a bit about the history of unix that I quite liked. I’m young and don’t know the whole story. According to this handbook, unix was used and taught in universities, so when students went out into the world they preferred unix systems. As a result, tons of companies started offering their own versions of unix touting portability with the other unixes but with their own differentiating extensions which sort of contradicts the claim of portability. People would write for one system and frustratingly find that their software doesn’t work on a different vendor. I’m curious where linux fits into the story. This must have been before linux because the handbook makes no mention of it. Did linux and its free software license immediately kill off these other unixes? How much role did copyleft play?

  • eah@kbin.socialtoLinux@lemmy.ml•Microsoft causes learned helplessness
    41·
    1 year ago

    I’ll offer a balanced position and say nobody can do it all themselves, but I think everyone should strive to be self-sufficient in at least one aspect of modern living. My neighbor grows their own food. My dad is good with cars. My aunt makes quilts and dishware. A society that has crafty knowledge widely distributed like this makes it more likely everyone knows an expert on a given thing, helping prevent people from getting screwed by terrible products. An Arch Linux user might be able to manage linux for 100 close people in their social graph, or at least advocate for it. This also keeps industry from having 100% market share.

  • eah@kbin.socialtoLinux@lemmy.ml•Canonical's Snap Store Hit By Malicious Apps
    2·
    1 year ago

    I have the issue that the snap version can’t browse files whose path includes a hidden dot file/directory in my home directory. It doesn’t seem there’s any clean way for me say “no, I give you explicit permission to read these files.” My workaround was to sudo mount --bind ~/.foo ~/bar and then browse from ~/bar instead. I’m not sure what they think they were preventing me from doing but they failed.