You are viewing a single thread.
View all comments View context
15 points

It’s easy to be backwards compatible when you’re backwards in general.

permalink
report
parent
reply
2 points

Well, better to be backwards with backwards compatibility than to just be backwards.

looks at Apple

permalink
report
parent
reply
7 points

I once heard some YouTuber say Windows uses \ in path names instead of / like everyone else because Microsoft thinks backwards.

permalink
report
parent
reply
4 points
*

As what often happens, using \ for paths is for backwards compatibility.

Neither CP/M nor MS-DOS 1.0 had folders. When folders were added in MS-DOS 2.0, the syntax had to be backwards compatible. DOS already used forward slashes for command-line options (e.g. DIR /W) so using them for folders would have been ambiguous - does that DIR command have a /W option, or is it viewing the contents of the W directory at the root of the drive? Backslashes weren’t used for anything so they used them for folders.

This is the same reason why you can’t create files with device names like con, lpt1, and so on. DOS 2.0 has to retain backwards compatibility with 1.0 where you could do something like TYPE foo.txt > LPT1 to send a document to a printer. The device names are reserved globally so they can work regardless of what folder you’re in.

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 2.6K

    Monthly active users

  • 1.1K

    Posts

  • 39K

    Comments