• AnAmericanPotato@programming.dev
    link
    fedilink
    English
    arrow-up
    28
    arrow-down
    1
    ·
    1 day ago

    Kind of the opposite. It takes more effort to make a filesystem case-insensitive. Binary comparison is the laziest approach. (Note that laziness is a virtue.)

    I’m on the fence as to which is better. Putting backwards compatibility aside, there’s a perfectly good case to be made for case-insensitivity being more intuitive to the human user.

    Apple got into a strange position when marrying Mac OS (case-insensitive) and NeXTSTEP (case-sensitive). It used to be possible to install OS X on case-sensitive HFS+ but it was never very well supported and I think they axed it somewhere down the road.

    • Raltoid@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      5
      ·
      edit-2
      1 day ago

      I can with very high confidence say that for the average computer user, case-insensitive is basically the only alternative. At least if you don’t want IT and computer support around the world to start going postal.

      As soon as someone is at least semi comfortable navigating a unix-style terminal and using a terminal based text editor to at least change config files, case-sensitive starts to become better. And often the more you get into programming, the more you get like Linus here and develop a hate.