Why does Windows use drive letters and backslashes?

The lineage between Unix → DOS → Windows is indirect but full of historical quirks that explain many of these odd choices, including the infamous backslash. Let’s unpack that story a bit.

---

🧭 1. The Lineage in Brief

• Unix (1969–1970s):
  Created at Bell Labs. It established the conventions of:
  • / as the directory separator
  • A single root /
  • Case sensitivity
  • A “mount everything under root” filesystem model
• CP/M (mid-1970s):
  A simpler operating system for early microcomputers (Intel 8080, Z80).
  It didn’t use / or \ for directories — because it didn’t have subdirectories. Files lived in flat spaces, with optional “user areas.”
  Example: A:FILE.TXT CP/M did, however, introduce drive letters — A: and B: — because early machines could only have one or two floppy drives.
• MS-DOS (1981):
  Microsoft bought QDOS (“Quick and Dirty Operating System”), which was itself a CP/M clone.
  So DOS inherited:
  • Drive letters (A:, B:, C:)
  • No real directory structure at first (it was added later)
  • Limited filename support (8.3 format)

---

🔤 2. Why Drive Letters Persisted

When hard drives and directories were added to DOS, the letter system was already entrenched.
It made sense to keep:

• A: and B: for floppies
• C: for the first hard drive

It was simple, easy to type, and required minimal memory or parsing logic — crucial on early PCs with 64 KB of RAM.

---

↩️ 3. The Backslash Mystery

Unix used /, and DOS initially did too.

Here’s what happened:

• Early DOS versions (1.0 and 1.1) didn’t have directories — only files.
• / was used as a command switch character: DIR /P /W (much like ls -l in Unix)
• When Microsoft added directory support in DOS 2.0 (1983) to mimic Unix, they suddenly needed a path separator.

But / was already in use for command options — and changing that would break compatibility with all existing utilities.

So they chose the backslash (\) as a substitute for / to separate directories:

C:\DOS\COMMAND.COM

This one design compromise in 1983 became an enduring legacy — one that’s still with us 40 years later.

---

💡 4. Why Unix Used / in the First Place

In Unix, / was simply the easiest printable character that wasn’t used elsewhere and made sense visually (a “slash through” directories).

• Early Unix terminals didn’t even have a backslash key!
• / also looked clean in listings like /usr/bin, which read naturally.

---

🧩 5. The Resulting Oddities

Concept	Unix/Linux	DOS/Windows
Root	/	Drive letters (C:\)
Separator	/	\
Option flag	-	/
Case sensitivity	Yes	No
Mounting	Unified tree	Per-drive roots

Ironically, modern Windows internally supports / in many APIs — you can actually use forward slashes in most file paths today — but it’s not widely known because of legacy expectations.

---

🧠 Summary

• Drive letters came from CP/M — simple and limited hardware.
• Backslash (\) was a workaround because DOS already used / for options.
• Unix’s / separator predates both and influenced the later directory concept in DOS.
• Windows kept DOS’s conventions for backward compatibility, long after they stopped making technical sense.

---