As a full time desktop Linux user since 1999 (the actual year of the Linux desktop, I swear) I wish all you Windows folks the best of luck on the next clean install 👍

…and Happy 30th Birthday “New Technology” File System!

  • sorenant@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    6
    ·
    edit-2
    1 year ago

    Are you writing parahraphs for folder/file names? That’s one “issue” I never had problem with.

    Maybe enterprises need a solution for it but that’s a very different use case from most end users.

    Improvements are always welcome but saying it’s “ridiculously short” makes the problem sound worse than it is.

    • Tekchip@kbin.social
      link
      fedilink
      arrow-up
      31
      ·
      1 year ago

      I think they mean the full path length. As in you can’t nest folders too deep or the total path length hits a limit. Not individual folder name limits.

    • RagingNerdoholic@lemmy.ca
      link
      fedilink
      English
      arrow-up
      25
      arrow-down
      1
      ·
      edit-2
      1 year ago

      File paths. Not just the filename, the entire directory path, including the filename. It’s way too easy to run up against limit if you’re actually organized.

      • Aux@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        32k Unicode characters. No, mate, it’s not easy to run up.

      • motorwerks@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        8
        ·
        1 year ago

        You like diving 12 folders deep to find the file you’re after? I feel like there’s better, more efficient ways to be organized using metadata, but maybe I’m wrong.

        • d3Xt3r@lemmy.world
          link
          fedilink
          English
          arrow-up
          16
          ·
          1 year ago

          Not OP, but I occasionally come across this issue at work, where some user complains they they are unable to access a file/folder because of the limit. You often find this in medium-large organisations with many regions and divisions and departments etc. Usually they would create a shortcut to their team/project’s folder space so they don’t have to manually navigate to it each time. The folder structure might be quite nested, but it’s organized logically, it makes sense. Better than dumping millions of files into a single folder.

          Anyways, this isn’t actually an NTFS limit, but a Windows API limit. There’s even a registry value[1] you can change to lift the limit, but the problem is that it can crash legacy programs or lead to unexpected behavior, so large organisations (like ours) shy away from the change.

          1. https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry
        • Riskable@programming.devOP
          link
          fedilink
          English
          arrow-up
          9
          ·
          1 year ago

          C:\Users\axexandriaanastasiachristianson\Downloads\some_git_repo\src\...

          You run into the file parth limit all the fucking time if you’re a developer at an organization that enforces fullname usernames.