- cross-posted to:
- hackernews
- cross-posted to:
- hackernews
You must log in or register to comment.
Its interesting to see how Linux-like NT paths are.
Drive letters <<< whatever Linux is doing << the Amiga approach to drives
Now I’m imagining someone making 💩: their default boot drive.
This behavior is actually in line with what I’d expect, as Unicode support in Windows predates UTF-16, so Windows generally does not handle surrogate pairs and instead operates almost exclusively on WTF-16 code units directly.
So it’s just straight UCS-2, and the software does enforce that, pretty much the opposite of “WTF-16”.
Edit: Pretty sure “modern” (XP+ I think) Windows actually does enforce UTF-16 validity in the system, but there’s always legacy stuff from the NT4/2K era that might turn up.
So? Who cares? Drive letters were always a dumb idea.
Also, obligatory “get your butt off of windows, switch to Linux.”
Drive letters. How quaint.
Windows. How quaint.
The Linux approach did take some getting used to, of course, but mounting drives to folders just makes too much sense. The only qualm I’ve had with it is if the drive doesn’t get mounted and stuff gets written to that folder, which, AFAIK, isn’t possible in windows.
Also, tbf (and balanced), windows also supports mounting drives to folders iirc, it’s just a weird way to do it.
Thanks for the share (pun intended)
That’s a nerdy-ass pun.
What’s drive letters?
In inferior operating systems they refer to mountpoints as “drive letters”. “C” is like “root”
Hard drive, e.g. C:, D:, etc. From what I gather from the headline
Drive Letters are also for removable media (floppy disks, CD/DVD drives, others [magneto-optical drives, etc), not to mention network drives. Not just Fixed Disks (hard drives).
It’s just an easy way to specify one disk from another.
Interesting read but I can’t think of much of a reason to ever use nonstandard drive letters except to maybe hide malware or something.
Maybe you have more than 26 storage devices, but don’t know how to use folder mounts on windows, or are weirdly attached to bad design decisions from the 1980s.
Yeah but as file explorer and even powershell can’t use the mount that 27th drive mounted to +:/ isn’t going to be very usable
One (contrived) example would be to have a drive that doesn’t have any installed file system filters on it. Filters being the hooks that windows, antivirus, etc have that intercept file writes and such. Could make it much faster on windows for that use-case. I can see custom software using that drive.
Contrived? Definitely. But potentially useful. I can see it working similarly to something MS has in testing which is the file system thing that is super fast but is limited in features—can’t seem to find it atm…
Edit: Found it. Dev drive via ReFS.
you can also mount it to a directory just like in POSIX systems
And is the default behavior once it runs out of “normal” drive letters I think.
