Windows Gets Linux — and It Actually Matters

The latest Windows build dropped this week with a genuinely surprising number of updates — but the one I keep thinking about is the introduction of the Windows Subsystem for Linux. This is not a small thing, and I want to take a moment to think through why.

WSL, to use the abbreviation that has already stuck firmly, allows you to run a Linux environment directly on Windows — without a virtual machine, without dual-booting, without any of the friction that has historically made running Linux tools on a Windows machine a fairly awkward proposition. You install it, you open a terminal, and you have a full bash shell. Ubuntu, specifically, with this release.

Why This Is Surprising

Let me be direct: five years ago, the idea of Microsoft shipping a Linux subsystem as a first-class feature of Windows would have seemed like a joke. Not a particularly funny one, but a joke nonetheless.

The Microsoft of the early 2000s was famously hostile to open source in general and Linux in particular. "Linux is a cancer," Steve Ballmer reportedly said in 2001. The relationship between the two worlds was adversarial in a way that felt deeply entrenched. Windows was the enterprise choice. Linux was what the server room ran when nobody was looking.

The transformation over the past several years under Satya Nadella has been remarkable to witness from inside the Microsoft ecosystem. The acquisition of GitHub, the embrace of open source, the "Microsoft loves Linux" messaging — these were not just marketing repositions. WSL is evidence that the cultural and engineering shift is real.

What It Actually Does

For developers working in Microsoft environments who also need to interact with Linux-based systems — and that is a lot of developers, given how much of cloud infrastructure runs on Linux — WSL removes a genuine pain point. No more spinning up a VM just to run a bash script. No more keeping a separate machine around for the Linux toolchain. No more compromises.

I have been using the command prompt as a guilty pleasure for years — I will admit that freely — and I know that makes me slightly unusual in a world that has largely moved to PowerShell. But WSL is addressing something different: it is not just about command-line comfort, it is about workflow integration. Developer toolchains that are native to Linux can now run alongside Windows applications, sharing the same filesystem, the same network, the same machine.

For those building cloud-native applications and deploying to Linux-based infrastructure — which, again, is a substantial proportion of modern development — that coherence matters.

A Broader Signal

I think the more interesting story here is what WSL represents about Microsoft's direction. The company is no longer trying to own the developer's entire stack. It is trying to be the best platform for developers regardless of where their work takes them — whether that is Windows, Linux, Mac, Azure, AWS, or somewhere else entirely.

That is a fundamentally different posture from the Microsoft of fifteen years ago. It reflects a recognition that developer allegiance cannot be commanded; it has to be earned, continuously, by being genuinely useful.

WSL is useful. Really useful. It is the kind of thing that, once you have it, you wonder how you managed without it.

The build notes this week had a lot of updates in them — security fixes, UI improvements, performance work. But WSL is the one I will still be thinking about in a month. It feels like a landmark moment in a quiet, understated way: the moment Windows became, genuinely, a great place to do Linux development.

That is worth noting.