Why Linux Dominates Servers: Historical, Technical, and Economic Factors

Historical Context: Windows Server's Early Popularity and Security Flaws

Around 20 years ago, the Windows Server + IIS + ASP + Access stack was widely used, especially for small business sites with low content-update frequency. A popular Chinese forum platform, Dvbbs (动网论坛) , ran on ASP + Access and was easy to install — often without even configuring ODBC. Later, the same vendor released Dvbbs.NET (动网先锋) using ASP.NET, and products like Doyoo (动易) that wrapped source code into DLLs to prevent theft. Hosting providers would explicitly advertise "Doyoo component support" for Windows plans, while Linux plans highlighted Zend Optimizer for PHPWind .

A critical security flaw emerged: virtual hosts typically provided a single root directory shared by web and FTP. Novice ASP developers often placed index.asp and data.mdb side by side. Since the MDB file was directly accessible via HTTP ( http://site/data.mdb), anyone could download the database, open the user table, and read plaintext passwords. The community workaround was renaming data.mdb to data.asp so IIS would execute it instead of serving it. Meanwhile, Linux hosts quickly adopted Zend support, while Windows hosts gained a reputation for ASP inefficiency, insecurity, and fragile MDB files (corruption leading to data loss).

IIS vs. Apache/Nginx/Lighttpd: Technical and Ecosystem Deficits

In the early 2000s, Windows Web Server had advantages: built-in FTP, ASP required no extra deployment, and GUI configuration suited junior administrators. However, IIS's closed architecture became a liability. It was tightly bound to ASP.NET, making deployment of PHP, Ruby, and other languages problematic — especially during the 2005 language boom when Apache compatibility far exceeded IIS. IIS's complex permission model and request lifecycle confused language runtimes.

Performance was another decisive factor. Nginx and Lighttpd , built on poll and epoll, were extremely lightweight and delivered several times the concurrency of IIS. IIS's overly complex, hard-to-debug configuration prevented many users from optimizing performance. These two issues — poor multi-language support and inferior performance — caused the web server market to shift decisively to Linux.

Modern Operational Experience: Game Server Deployment

A recent hands-on comparison: setting up a Palworld dedicated server on Windows Server required hunting for specific VC++ and DirectX runtime installers, which were difficult to locate. Switching to Ubuntu reduced the process to apt install steamcmd and running server.sh. For a 4–5 player Minecraft server, typical VPS sizes are 2C2G or 2C4G. Running Windows on 2 GB is nearly impossible; on 4 GB the OS consumes a large RAM fraction, making Linux the pragmatic choice for lightweight workloads.

Licensing Cost

Windows Server licenses are priced per CPU core, costing roughly 100,000 RMB per server for legitimate authorization. Linux is free.

Ecosystem, Lightweight Distros, and Containerization

Ecosystem momentum is self-reinforcing: by the time .NET Core arrived, Java, Go, and Node.js had already partitioned the server-side landscape. Lightweight distributions like Alpine Linux enable minimal container images, making deployment more flexible and efficient. Containerization itself is a Linux-native technology (namespaces, cgroups); Windows and macOS face architectural constraints that prevent containers from running at the same low level. Since containerization is now unavoidable in server architecture and operations, Linux's native support makes it the default choice.

Microsoft's Historical Opposition to Open Source

Bill Gates' 1976 "Open Letter to Hobbyists" expressed hostility toward unpaid software use, questioning who would invest man-years without compensation. Microsoft's revenue model relied on selling Windows and Office licenses, peaking in 1999 as the world's most valuable company. The early open-source community was largely academic — universities that had early computer access. Microsoft won the first phase (desktop) by efficiently delivering a complete proprietary stack. But in the second phase (servers), Microsoft's insistence on paid licensing clashed with the open-source model that leveraged internet distribution to build a new ecosystem. The two camps were ideologically opposed for years; Microsoft has since embraced open source, but the server market had already standardized on Linux.

Path Dependence and the Matthew Effect

One respondent argues the question conflates "why servers use Linux now" with "why history chose Linux." The current answer is mature solutions, abundant tooling, and easier maintenance. The historical answer is cost avoidance — but the competitor was not Windows; it was proprietary Unix. Linux (1991) was just a kernel, yet it ran Unix-compatible software and commands, enabling seamless, free migration. Windows NT (1993) and its popular Server 2000 arrived when mindshare had already shifted to free Linux. The analogy: learning Red Hat led directly to ops jobs; learning Windows Server offered no comparable practice environment. This Matthew effect — early adoption begetting more adoption — locked in Linux's dominance.