Why Microsoft Almost Adopted the Forward Slash for Windows Paths

Developers who switch between macOS and Windows quickly notice that macOS uses /Users/xxx/Documents while Windows uses C:\Users\xxx\Documents. The single character difference—forward slash versus backslash—forces countless uses of path.join, os.path, or pathlib in cross‑platform code.

The story begins with Unix. In the early 1970s Ken Thompson and Dennis Ritchie chose / as the directory separator because it was readily available on the keyboard and did not clash with other symbols. This convention was baked into Unix, later inherited by Linux, macOS, Android and virtually every OS except Windows.

Before Unix, DEC’s TOPS‑10 used / as a command‑line parameter prefix. For example, DIR /W displayed a wide listing, analogous to the modern Unix - flag. Engineers who grew up on TOPS‑10 carried this habit into later jobs, including positions at IBM.

When Tim Paterson wrote 86‑DOS (later MS‑DOS) in 1980, the system had no sub‑directories; all files lived in the root. Consequently, / remained a parameter prefix in commands such as DIR, FORMAT, and COPY. IBM engineers, accustomed to the TOPS‑10 convention, continued to use / in these utilities.

MS‑DOS 2.0 (1982‑1983) introduced a hierarchical file system, creating the need for a path separator. Microsoft’s engineers naturally wanted to reuse the Unix /. IBM objected because millions of existing DOS programs already interpreted / as a switch; changing it to a directory separator would break compatibility for countless shipped PCs and third‑party software.

Faced with IBM’s resistance, the two companies searched for an unused, keyboard‑friendly character. The backslash \ was the only viable candidate, so the compromise was made: Windows would adopt \ as the path separator, while Unix retained /. The decision was finalized in 1983.

Later Windows versions (e.g., Windows NT) added APIs that accept forward slashes— C:/Users works in many Win32 calls—but the command shell ( cmd.exe), PowerShell, and Explorer continued to display and require backslashes. Changing the convention now would affect hundreds of thousands of legacy scripts, registry entries, SDKs, and enterprise systems that have relied on \ for three decades.

Thus, the backslash is not a technical necessity but a legacy of a 1983 compatibility promise to IBM. It remains a subtle reminder that a single character can separate two computing worlds, shaped more by business negotiations and developer inertia than by technical merit.