1. 21
  1.  

  2. 7

    This only affects case-insensitive filesystems that support symbolic links, so it shouldn’t impact people on normal behaving Unix-like systems.

    1. 9

      Notable exception is macOS.

      1. 7

        To give a more helpful response than the other responses to you, in the era of APFS I’ve taken to creating an APFS volume formatted as case-sensitive and keep my git repos there.

        This allows applications like git, which usually expect a case-sensitive filesystem, to work correctly, while the OS or other applications can keep the case-insensitive filesystem.

        I came up with this strategy from working on shared git repos, where occasionally a user using a case-sensitive filesystem might push two different (to them) branches, such as feature/foo and feature/Foo, but git pull on a default case-insensitive macOS filesystem made git get quite upset.

        I think it’s also worth noting that case-insensitive is a pretty reasonable default on systems like Windows and macOS, which largely target non-technical users who don’t want to be baffled by two files apparently being called the same thing. Sure, us technical folk get it, but we’re very much not in the majority. Calling behaviour that’s intended to be helpful for the majority, “gimped” is unkind and misinformed.

        1. 6

          Even as a technical person who is totally comfortable with case-sensitive filesystems, I prefer case insensitivity. Filenames are first and foremost a way to label sequences of bits for the benefit of humans, and are usually generated by humans. So ideally they should have human-friendly semantics, not less-work-for-the-filesystem-programmer semantics.

        2. 7

          “Normal behaving Unix-like systems,” not “gimped Unix-certified systems!”

          1. 14

            I don’t think this attitude really benefits anyone.

            1. 3

              It was snarkily put, but the message is valid. Personally I have never understood how hackers handed a virtual monopoly to Apple after Microsoft’s crumbled.

              There was a brief period when Microsoft was losing their stranglehold, and during that time, hackers fled not to Linux or BSD, but … to another proprietary system, this time tied to a massive hardware and software walled garden.

              1. 11

                They “fled” to another proprietary system because that system could give them something the free systems could not: Ease of use.

                1. 7

                  Ease of use.

                  This is it. I am all-in on the Apple ecosystem in the last two years after stubbornly clinging to Linux (various distros) for almost two decades. At some point I just couldn’t handle the constant state of partial-brokenness any more. I have more interesting shit to do than figure out why I can’t share my screen properly on a video call or why the audio stops working every other day. Network effects were part of it, I’ll admit, but since I switched, and really embraced the OS, I am happier and more productive.

                  1. 3

                    I disagree, as someone who was using both Windows, MacOS, and Ubuntu systems at the time in a commercial setting.

                    The Linux systems just worked. Back in the days before Docker and friends, you could write a simple script to take a vanilla Ubuntu installation and set it up as a dev machine while you grabbed coffee. Meanwhile, the team I was on spent much effort trying to do the same with MacOS, and still wound up with a bunch of manual faffing around.

                    Furthermore the systems themselves weren’t user serviceable or upgradeable. A few years after the previous experience, I started work with a new client. To my immense displeasure, their ‘local dev environment’ involved installing a ~ 30GiB SQL Server VM, back when that was large. Several of my colleagues literally had to buy new laptops; I just popped down to JB HiFi during lunch, bought a new hard drive, and had swapped it in with time left over for coffee :)

                    Nowadays, I’m running a MacBook Pro w/ Catalina (client machine), and a ThinkPad W540 w/ Ubuntu (personal machine). Again, the Ubuntu experience is vastly superior. I don’t get crashes when I enable my Bluetooth headset mid-Zoom. The MacOS system mysteriously hangs - but only sometimes - when I open the lid, or when I try to log in. The Ubuntu system … just works.

                    And I’m not just considering this from the point of view of a developer. My mother in law bought a new Windows laptop after years of running Ubuntu quite painlessly, and it has given her no end of trouble. The most recent was a conflict between a WiFi driver update and the Windows power saving settings - which manifested as the WiFi ‘going away’ after a few minutes at idle, and not coming back. Took me the best part of an hour to debug.

                    Perhaps by ease of use you’re referring to the Apple ecosystem as a whole? Where you have an Apple watch, an Apple phone, an Apple laptop, an Apple TV … ? Not having experienced that myself, I can imagine that the ease of use of a tightly integrated system could outweigh the costs, especially for inexperienced or non-technical users.

                    1. 4

                      Not having experienced that myself, I can imagine that the ease of use of a tightly integrated system could outweigh the costs, especially for inexperienced or non-technical users.

                      Even as an experienced, technical user (whose daily tasks usually involve large C codebases, and not, say, using Adobe products), having a MacBook, iPhone and Apple TV lets me effortlessly coordinate my ~personal area network~ in ways that are extremely efficient and honestly, pleasurable/joyful. (It helps that my partner uses Apple devices too.) I still do have a FreeBSD desktop but I mostly use it through ssh from my MacBook.

                      I’ll be frank: I don’t love what it represents. But this lets me get on with my life much more effectively than trying to scout out what the least worst Linux laptop is, the least-crappy Android OEM, etc. etc.

          2. 1

            ZFS datasets can be set to case-insensitive, but only on dataset creation. Case-insensitive datasets are usually created when setting up corporate SMB/CIFS shares.