Windows-versions inherit the odd system of disk drive letters from the old CP/M
Unix-versions (Solaris, Linux, BSD, BeOS, MacOS X, NextStep, ...) don't have this nonelastic system of drive letters for addressing. The file system is here independent of the hardware. The hardware (disks, floppies, cdroms, ram, ...) cant be mounted via mountpoints in the file system.
why you are pushing your preference as some indisputable truth? that system with using say "forest" of FS hierarchy trees with each own root, marked with the letter, instead of just one is not "odd". not for everybody. for example I like it way more, than the nuxi approach. and oppositely, I do dislike the nuxi one tree approach. I want to see my storage volumes clearly, and "lettering" drives allow me this. whereas dissecting unix one tree with something like mount -l just spits tons of garbage in the face. forest of trees is more convenient to use for an interactive user, that is for a human.
don't have this nonelastic system of drive letters for addressing. The file system is here independent of the hardware
seriously, how drive letters are "non-elastic" and "hardware dependent"? the only difference, that unix glues all the volumes together in one tree for a user, whereas Windows represents every volume as it is - a standalone tree, so you have a forest of trees. if you are more used to the unix variant, that is ok, but it doesn't make it more "elastic" and "hardware independent", whatever you meant by that.
questions like "why reactos/windows is not like unix" are nonsense. statistically all variants of forum questions may exist, so you ask nonsense, other one asks good questions, that are helpful for them or others, the third is just a spammer. the same is with OS approaches - Windows uses a cool approach for reopresenting storage to the user, unix clones use a sucky one.
will ReactOS support the sucky unix approach? you got the answer - ReactOS aims to be very compatible with Windows, so if there some decides to put this into Windows, then eventually it will be available in ReactOS. but maybe you are better off to keep using your NextStep if you love it so much?
Otherwise you can use NT device paths, for example: \??\Device\HarddiskVolumeN (with N a number) and you get the same system as *nix systems too.
I suspect, then they will be dissatisfied with using backslash. because unix cannot use both as a delimiter. doh. maybe slash is more elastic?
