• BigDanishGuy@sh.itjust.works
      1·
      3 minutes ago

      What is this “real” concept anyway?

      Adam Savage famously stated on Mythbusters “I reject your reality and substitute my own”

      Sure, but is reality even real then? Is anything real?

      Not that I meant to get all pop-philosophical on this beautiful Sunday morning, sorry about that.

  • atx_aquarian@lemmy.world
    39·
    5 hours ago

    Fun fact, though: Linux is the only case-sensitive one.

    Edit: I feel silly for forgetting that it’s all about the choice of FS. If anyone needs anything from me, I’ll be in the corner, coloring.

    • frezik@midwest.social
      1·
      17 minutes ago

      I once ran into a bug in an Arduino program where it wouldn’t compile. The author blamed my “broken environment”. Turned out, he had included “arduino.h” instead of the correct “Arduino.h”.

    • Localhorst86@feddit.org
      28·
      3 hours ago

      From a technical standpoint, the windows NTFS filesystem is designed inherently case sensitive, just windows doesn’t allow creating case sensitive files.

      Connecting an NTFS drive to linux, you can create two separate files readme.txt and Readme.txt.

      Using windows, you can see both files in the filesystem, but chances are most (if not all) software will struggle accessing both files, opening readme.txt might instead open Readme.txt or vice versa.

      • pixelscript@lemm.eeEnglish
        6·
        2 hours ago

        For a few years now, Windows has had the capability of marking certain directories as case-sensitive. So you can have a mixed-case-sensitivity filesystem experience now. Yeah. :/

      • SaharaMaleikuhm@feddit.org
        121·
        3 hours ago

        Case-insensitive filesystems are for maniacs. They are only causing trouble. Ever had two folders with the same name but different capitalization in windows? You see both, but whichever you click it will always open the same one, while the other can’t be accessed. Psychopath behavior.

        • ahornsirup@feddit.org
          1·
          53 minutes ago

          That’s because NTFS isn’t case-insensitive. If it was there’d be no two folders. Windows is a case-insensitive operating system running on a case-sensitive file system. It’s pretty clear Microsoft wanted case sensitivity and then realised how much legacy software that’d break.

      • Trainguyrom@reddthat.comEnglish
        10·
        4 hours ago

        Makes changing the case of a file/folder a lot easier though. Windows you have to rename it to something else then rename it again just to change case but Linux you can just…rename it. It’s a small thing but it’s something

      • paperplane@lemmy.world
        9·
        5 hours ago

        When case insensitivity is the default I always wonder how many apps unknowingly rely on that due to typos somewhere. I encountered this once while porting a Windows/macOS app to Linux that someone imported a module with the wrong case and nobody noticed

  • umbraroze@lemmy.world
    191·
    9 hours ago

    I don’t really watch Star Wars. I’m a more of a Trekkie gal.

    🖖

    See, you can separate files both ways as long as it’s logical

  • pelya@lemmy.world
    42·
    11 hours ago

    You can actually use / as a path separator on Windows in functions like fopen(), because it supports some ancient version of POSIX standard.

    • palordrolap@fedia.io
      25·
      10 hours ago

      There used to be an undocumented setting in early versions of MS-DOS that would allow the setting of the command option character to something other than the slash, and if you did that, the slash automatically became the path separator. All you needed was SWITCHAR=- in your CONFIG.SYS and DOS was suddenly very Unix-y.

      It was taken out after a while because, with the feature being undocumented, too many people didn’t know about it and bits of software - especially batch files, would have been reliant on things being “wrong”. The modern support for regular slash in API calls probably doesn’t use any of the old SWITCHAR code, but it is, in some way, the spiritual descendant of that secret feature.

      Here’s an old blog that talks about it: https://learn.microsoft.com/en-gb/archive/blogs/larryosterman/why-is-the-dos-path-character

    • marcos@lemmy.world
      9·
      9 hours ago

      The one thing about NT was that it didn’t have it’s own semantics, but it could emulate any system you wanted. It’s the unofficial successor of an OS that was based on creating VMs where you could run any other OS you want.

      Then Microsoft decided to create their own system in it, and only really finished writing that one.

    • SatyrSack@feddit.orgEnglish
      26·
      10 hours ago

      And BSD. It’s really just Windows vs. literally everything. Or is there anything else that uses backslashes?

    • mercano@lemmy.world
      8·
      8 hours ago

      Only Mac OS 10 and later, based on BSD, uses ‘/‘. (And, I guess, A/UX.) Classic MacOS used a ‘:’, but it wasn’t regularly exposed in the UI. The only way most users would know is that the colon couldn’t be used in a file name.

      • horse@feddit.org
        2·
        4 hours ago

        I might be wrong, but I think you still can’t use a ‘:’ in a filename in macOS. If I recall correctly it will let you do it and show it in Finder, but actually replace it with a ‘-’.

  • RedSnt@feddit.dk
    3·
    8 hours ago

    If you know what a nordic keyboard layout looks like, you’d probably prefer backslash. Since I moved to Linux a year ago I’ve been struggling to find the easiest way to forward slash. Shift + 7? Or numpad / with my right pinky?

    • bricked@feddit.orgDeutsch
      4·
      4 hours ago

      For me it’s even worse. Forward slash is also Shift + 7 and backslash is AltGr + ß?? I hate that computing is only optimized for US american layouts. Going by my keyboard, the filepath separator should probably be an ö.

    • dan@upvote.au
      3·
      8 hours ago

      Get a macro pad and configure one button to type a forward slash.

      How do you type URLs using that keyboard layout?

      • RedSnt@feddit.dk
        5·
        7 hours ago

        Shift+7 feels wrong for some reason, so I currently tend to just send my pinky on a kamikaze mission towards the numpad hoping I hit /. Sometimes I hit numlock, sometimes I hit *.
        Even if I made a compose key “shortcut” via ~/.XCompose it’d still be more work than what I’m doing already.

        Macro pad could be a solution, I have considered it beforehand for other purposes tbh

    • Diplomjodler@lemmy.world
      66·
      11 hours ago

      Linux uses forward slash. Windows uses backslash. Because some dude 45 years ago wanted to make it look different from UNIX.

        • PNW_Doug@lemmy.world
          17·
          11 hours ago

          They did! And I weirdly kind of miss them for the entirely non-logical reason that they looked elegant.

          Don’t get me wrong, I adapted in about 3 seconds when I made the switch to Mac OS X 25 years ago, but I irrationally kinda miss them just a tiny bit.

        • __nobodynowhere@startrek.websiteEnglish
          19·
          10 hours ago

          DOS originally didn’t even support directories but was using / for command line arguments. They didn’t want to change the option character and break stuff so they went with \ as the directory separator.

          DOS wasn’t originally created by Microsoft. They bought the OS from computer shop in Seattle.

  • Black History Month@lemmy.world
    19·
    5 hours ago

    I love linux like a pet. I love windows like my car. Can we stop with this pointless making a content mountain over any insignificant difference. Don’t get me started