Imagine a world where Windows and Linux seamlessly intertwine, where developers can harness the power of both ecosystems without compromise. This is the story of Microsoft's Windows Subsystem for Linux (WSL), a journey that began over a decade ago and recently culminated in a groundbreaking open-source transformation. At the Ubuntu 25.10 Summit in London, Craig Loewen, Microsoft’s senior product manager for WSL, and Clint Rutkas, principal product manager lead at Canonical, unveiled the fascinating tale of WSL’s evolution from a closed, proprietary project to a thriving open-source community asset. But here's where it gets controversial: could Microsoft, once a staunch advocate of proprietary software, now be leading the charge in open-source innovation? Let’s dive in.
The Unlikely Beginnings: From Project Astoria to WSL
WSL’s origins trace back to 2010 with Project Astoria, an ambitious but ill-fated initiative aimed at running Android apps on Windows Phone. While the project never saw the light of day, it laid the groundwork for something far more impactful. The initial prototype translated Linux system calls into Windows NT kernel calls, a concept that would later become the foundation for WSL. Fast forward to 2016, and Microsoft, in collaboration with Canonical, launched Bash and Ubuntu on Windows, allowing Linux binaries to run natively on Windows. Dustin Kirkland, then at Canonical, described it as a breakthrough: “We’re talking about bit-for-bit, checksum-for-checksum Ubuntu ELF binaries running directly in Windows.”
WSL 1.0: The Compatibility Layer
WSL 1.0, released in 2017, was a compatibility layer that enabled Linux distributions like Ubuntu, openSUSE, and Fedora to run on Windows by translating Linux system calls into Windows NT kernel calls. This was achieved through a mechanism called pico processes, which, while innovative, had one major drawback: speed. Developers loved the idea but found it sluggish. And this is the part most people miss: WSL 1.0 was just the beginning, a stepping stone to something much bigger.
WSL 2.0: A Paradigm Shift
Microsoft listened to the feedback and took a bold step. Instead of relying on emulation, they developed their own Linux kernel, introducing WSL 2.0 in 2020. This version used a lightweight virtual machine (VM) to run the Microsoft Linux kernel, updated seamlessly via Windows Update. The result? A massive surge in popularity. By 2022, the percentage of developers using WSL as their primary operating system had skyrocketed from 3% to over 14%, according to the Stack Overflow Developer Survey. But why stop there? The real game-changer was yet to come.
The Push to Open Source: A Cultural Shift at Microsoft
Internally, WSL’s developers began advocating for open-sourcing WSL 2.0. As Loewen put it, “Linux is open source, and we’re working on a Linux product. It makes sense to be where the community is.” However, this wasn’t an overnight decision. WSL was initially tightly coupled with the Windows kernel, making open-sourcing a complex challenge. Years of effort went into decoupling private APIs and refactoring dependencies. Rutkas admitted, “Open sourcing is rewarding, but it takes time and effort. You must convince your stakeholders.”
The Open-Source Revolution: Immediate Impact
When WSL finally went open source, the response was electric. Within a day, GitHub stars doubled from 15,000 to over 30,000, and it became the top post on Hacker News for 24 hours. This wasn’t just a technical achievement; it was a cultural shift. Microsoft proved that open source could drive innovation faster than proprietary models, empowering developers worldwide to contribute and improve WSL at an unprecedented pace.
A Blueprint for the Future
WSL’s open-source journey has become a blueprint for other Microsoft projects, including Windows Terminal, PowerToys, and the new CLI editor, Edit. But here’s the thought-provoking question: Can Microsoft truly become a leader in open-source software? A decade ago, this would have seemed absurd. Today, it’s a reality worth discussing. What do you think? Is Microsoft’s embrace of open source genuine, or just a strategic move? Share your thoughts in the comments below!
