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!

all 22 comments

sorted by: hot top controversial new old
[–] 3 points 3 years ago (2 children)

How do you know when someone uses linux?

Don't worry, they'll tell you

  • source
  • hideshow 4 child comments
  • [–] 0 points 3 years ago (1 child)

    I wouldn’t tell you if I use Linux. I would tell YOU to use Linux. That reminds me… use Linux!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (2 children)

    We have extra time to diss Windows since we don’t have to wait for our OS to reboot all the fucking time.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 3 years ago

    Omg. This hits home. I think Linux has prompted / asked me to reboot one time since I installed it 2 months ago. Windows wants you to reboot everytime you change anything. I didn't realize how insanely often it asks until I had something to compare it to.

    I got a friend trying Linux for the first time and they asked for some help picking software to install, like which office suite or photo app etc... They just instinctively rebooted after everything they did like it was a pavlovian response, lol.

  • source
  • parent
  • [–] 2 points 3 years ago (1 child)

    You want your filesystems to be old and stable. It's new filesystems you want to view with suspicion.. not battle tested.

  • source
  • hideshow 2 child comments
  • [–] 1 point 3 years ago

    I wouldn't really say so. Of course it's not a good idea take the absolutely latest system as your daily driver since it's propably not bugproof yet but also you don't want to use something extremely old just because it's been tested much more because then you're just trading away perfomance and features for nothing. For example ext4 is extremely reliable and the stable version is 15year newer than NTFS.

  • source
  • parent
  • [–] 1 point 3 years ago (2 children)

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

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 3 years ago (1 child)

    I think I've spotted the real problem.

  • 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.

  • 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.

  • source
  • parent
  • hideshow 2 child comments