Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One big issue is still the 260-character path-name limitation. Deep source directories choke on that, especially if you copy them around for backup, etc.

You end up abbreviating class names in the file names and mess up searchability.

You end up using single letter directories like 'C:\b\' instead of 'C:\backup\', etc. as workarounds. It all feels very MS DOS.



It looks like that's one of the things that they've finally, finally fixed (but only if you turn it on): https://mspoweruser.com/ntfs-260-character-windows-10/


yeah, and break all apps that use the old 255 char win32 api's.

another thing to note is that it requires the windows insider preview, which in my experience required auto reboots every few days. very frustrating so I had to revert....

Switching off of Insider Preview is a TERRIBLE experience of it's own: You can't actually revert back. you either have to restore from backup (which isn't mentioned when you switch to insider preview mode) or wait for the next mainline release, which may be 6+ months away, and you have to MANUALLY TRACK when insider syncs with main and then switch to main during the window in which they are matched.


If it is only fixed if you turn it on, it isn't really fixed yet IMO. You can't make public projects rely on it, etc. without turning off a big percentage of your users.


This limit never existed in the NT kernel, it's a Win32 SubSystem limit that can be workarounded with \??\ at the beginning of the path


Windows no longer has that limit since a decade at least.


I hit this on windows 8. So, there might might be a workaround, but it's still an issue for most users.


The limit is enforced unless an application ops out of it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: