• atx_aquarian@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    1 hour 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.

  • Black History Month@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    5
    ·
    edit-2
    1 hour 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

  • umbraroze@lemmy.world
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    5 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
    link
    fedilink
    arrow-up
    33
    ·
    7 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
      link
      fedilink
      arrow-up
      20
      ·
      6 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
      link
      fedilink
      arrow-up
      7
      ·
      5 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.

    • mercano@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      4 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
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        7 minutes 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 ‘-’.

    • SatyrSack@feddit.org
      link
      fedilink
      English
      arrow-up
      21
      ·
      6 hours ago

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

  • RedSnt@feddit.dk
    link
    fedilink
    arrow-up
    2
    ·
    4 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?

    • dan@upvote.au
      link
      fedilink
      arrow-up
      2
      ·
      4 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
        link
        fedilink
        arrow-up
        3
        ·
        3 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
      link
      fedilink
      arrow-up
      63
      ·
      7 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
          link
          fedilink
          arrow-up
          16
          ·
          7 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.website
          link
          fedilink
          English
          arrow-up
          16
          ·
          edit-2
          6 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.