Re:Environment Variables and Path in Windows 10
by kevingadd on Monday October 26, 2015 @03:43AM
(#10450002)
NTFS 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.
Re:Environment Variables and Path in Windows 10
by cm2187 on Monday October 26, 2015 @04:08AM
(#10450056)
I 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?
Re:Environment Variables and Path in Windows 10
by kuschku on Monday October 26, 2015 @05:27AM
(#10450259)
It is good to have case sensitivity in the file system, and insensitivity in the UI.
Re:Environment Variables and Path in Windows 10
by Someone1234 on Monday October 26, 2015 @10:20AM
(#10451596)
Why? The person above at least gave an example of why not, you're just simply stating the contrary without any explanation.
Re:Environment Variables and Path in Windows 10
by kuschku on Monday October 26, 2015 @01:11PM
(#10452756)
The 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 Í.
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.