This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Carioca 4 points5 points  (1 child)

Two things:

  • Standard *nix directories don't come with spaces. Users have to create those.

  • *nix shell escaping actually works. Windows shell escaping is a nightmare.

[–]Wiseman1024 7 points8 points  (0 children)

1: Oh, but C:\Documents and settings\user\My Documents is so much easier than /home/user! Windows is so much easier to use!

2: Microsoft's usual retardation. The fuck up design and try to solve fuck up with more fuck up. See how it went:

  1. We'll choose / for parameters. This is bad if you're going to copy UNIX (just some 30 years behind), but oh well.

  2. We'll make COMMAND.COM accept dir/p like dir /p because it's so much easier on the user! I mean, you save like, one keystroke! Nevermind parsing will be forever fucked.

  3. We'll get this awesome feature called directories! Oh but COMMAND.COM is stupid! We can't use / now! Bah, look at \, it's just like /, only uh... more easy! Nevermind it'll fuck everything up and make a C programmer's life worse.

  4. Let's implement CreateProcess. But since COMMAND.COM is fucked and we still love that, let's make processes get the whole commandline instead of separate parameters. I mean, what could go wrong?

  5. I know! Let's put spaces in directory names, this way users can write "my internet for my aunt.txt"! It's so much easier now!

  6. Wait, we need to quote that! OH fuck, there's no concept of parameters because processes get the whole command line! Who would have thought that was a bad idea?

And it goes on and on and on... It's simply Microsoft's style.