7
NTFS turns 30 years old today! I hear it's still in use by some crufty old legacy operating systems ๐Ÿ˜ (en.wikipedia.org)
submitted 3 years ago by to c/technology@lemmy.world
22 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 1 point 3 years ago (2 children)

Unbelievably, Windows still has a ridiculously short filepath length limit.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [โ€“] 0 points 3 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 0 points 3 years ago* (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] 1 point 3 years ago (1 child)

    It might be 255 characters for the entire path?

    I've run into it at work where I don't get to choose many elements. Thanks "My Name - OneDrive" and people who insist on embedding file information into filenames.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 1 point 3 years ago

    The limit was 260. The OS and the filesystem support more. You have to enable a registry key and apps need to have a manifest which says they understand file paths longer than 260 characters. So while it hasn't been a limitation for awhile, as long as apps were coded to support lesser path lengths it will continue to be a problem. There needs to be an conversion mechanism like Windows 95 had so that apps could continue to use short file names. Internally the app could use short path names while the rest of the OS was no longer held back.

  • permalink
  • fedilink
  • source
  • parent
  • [โ€“] 0 points 3 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] [S] 0 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 0 points 3 years ago (1 child)

    I think I've spotted the real problem.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 0 points 3 years ago (1 child)

    People have been talking about the real problem from the beginning of the thread: small character limit on file paths.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 0 points 3 years ago* (last edited 3 years ago) (1 child)

    I would be pissed if they made me use such a ridiculously long login name at work. Mine is twelve characters and that's already a pain in the ass (but it's a huge company and I have a really common name, so I guess all the shorter variations were already taken).

    Edit: Also, I checked it's really very simple to enable 32kb paths in recent versions of Windows.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •