• hackris@lemmy.ml
    link
    fedilink
    arrow-up
    9
    arrow-down
    2
    ·
    1 year ago

    Yep, this sort of behaviour translates to Windows paths also. Why would they name a directory “C:\Users\Example\Desktop”, when they can replace “Desktop” with a locale-specific name, which is not just a link to “Desktop”, but a completely different directory which breaks any scripts expecting “Desktop”.

    We know MS well, their choice is clear :)

    • PixxlMan@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      1 year ago

      It’s just… Why?

      Was there a thought process applied here at all? Worse still is that many of these localised paths are actually lies. They still use the original developer version in order to not break compatibility with programs, but refuse to admit it in the explorer. It’s maddening.

      • hackris@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Yep, and when you try to troubleshoot shit, it all falls apart and you can’t really tell what’s going on under the hood…