2 ms·
Unfortunately (or fortunately depending on your perspective) Microsoft takes a very "lowest common denominator" approach to backwards compatibility. A LOT of t
by Someone1234 12y ago
Unfortunately (or fortunately depending on your perspective) Microsoft takes a very "lowest common denominator" approach to backwards compatibility.
A LOT of third party software would definitely be broken if they altered Windows filename restrictions. They would also have to drop support for FAT32 as you pointed out.
Right now a lot of Windows 95 software continues to run 20 years later. And in no small part because of this type of attitude and all the runtime patching Microsoft does.
- ethomson 12y agoThey did alter the Windows filename restrictions. You can happily create a file that is 1000 characters long, and your Windows 95 software will likely refuse to open it. (Hell, Windows Explorer refuses to deal with it.) Now we've got a situation where we keep crowing about how changing MAX_PATH would break compatibility. Except, of course, that we already did that by adding the stupid '\\?\' APIs (which are themselves a mess). So now we don't actually have backward compatibility for those programs (we just make it so hard to use long paths that we virtually have backward compatibility.) And we have file paths that resemble 1995. We don't have the lowest common denominator, we just have the worst of both worlds.
- Someone1234 12y agoFair enough. I'm surprised with Metro/Modern/RT/whatever's APIs they didn't try and move forward by utilising \\?\ in Windows.Storage.*. But from what I've been able to tell they have the same limitations as other .Net or Win32 APIs.
- asveikau 12y ago> They would also have to drop support for FAT32 as you pointed out. This is a little dubious. When you load a FAT driver on a *nix system, you get the limitations of FAT. Likewise there are lots of fancy filesystem APIs in Windows that fail on a FAT volume and work on NTFS. That said, there are a lot of quirky NTFS behaviors that are ultimately rooted in FAT. I used to get frustrated by a lot of them, then I started writing a FAT driver just for fun ... and it made sense. All the goofy things about naming start to make sense if the direntry "is your inode" and the extra space in the name is padded with spaces...