News for hackers. Stuff that matters.

A comment on Environment Variables and Path in Windows 10. Parent comment

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.

[ Parent | on HN ]
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?
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.
[ Parent | on HN ]
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 Í.

[ Parent | on HN ]
Re:Environment Variables and Path in Windows 10 by frik on Monday October 26, 2015 @06:07AM (#10450404)
NT kernel and NTFS supports that, it can be activated.
[ Parent | on HN ]