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!
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 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.
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.
I think I’ve spotted the real problem.
People have been talking about the real problem from the beginning of the thread: small character limit on file paths.
The limit is 32,000 characters.
Only if you go into settings, disable the safety measures and change it. And some apps might break.
No, the default file path limit is 256 characters. And I don’t mean file name. Full file path.
No, you don’t need to change any settings, that’s the thing! Windows, unlike other OSes, has several APIs. Old apps (and dumb apps) are using old API and are limited to 260 characters. New apps are using new API and are limited by 32k characters. This “new API” is available since NT4, btw.
I remember I had to change a setting when using Windows. And it even showed me an “Are you sure?” dialog. It wasn’t that long ago. Is that not a thing anymore?
Once again, that only affects old or dumb apps. Any half decent app supports 32k paths since late 1990-s.