4 ms·
The 260 chars file path limit is a huge pain point for me personally, since I do most of my development in a Vagrant Ubuntu VM for the portability and superior
by lewisl9029 11y ago
The 260 chars file path limit is a huge pain point for me personally, since I do most of my development in a Vagrant Ubuntu VM for the portability and superior tooling support.
I wish Microsoft would just put their support behind one of the popular open-source filesystems and release it as an alternative filesystem for Windows. This plus an officially supported NFS server and a POSIX compatible API would dramatically increase the viability of using Windows natively for development.
- kevingadd 11y agoNTFS is honestly a great filesystem. Most of the stuff people dislike is due to the Win32 layer on top. For example: NTFS is case sensitive. NTFS does not have a 260ch path limit. The slowness of stat() (or at least part of it) is due to the inefficient way Win32 does filesystem enumeration/status queries.
- cm2187 11y agoI am not sure case sensitivity is a good thing. Do you really want users to wonder what is the difference between toolxyz.exe and Toolxyz.exe? How do they even google that?
- kuschku 11y agoIt is good to have case sensitivity in the file system, and insensitivity in the UI.
- frik 11y agoNT kernel and NTFS supports that, it can be activated.
- Someone1234 11y agoWhy? The person above at least gave an example of why not, you're just simply stating the contrary without any explanation.
- kuschku 11y agoThe user wants to have the ability to use both cases, but to support legacy software, it might be necessary to support cases. Also, upper/lowercasing is not defined the same in all languages. In turkish, i becomes uppercase Í.