You remember the ’90s, right? Or maybe you don’t — and that’s exactly the problem.
Back then, Linus Torvalds said something about Microsoft that everyone laughed off as paranoia. He said their strategy was simple: embrace a standard, extend it with proprietary hooks, and then extinguish the competition by making the original irrelevant. He wasn’t guessing. He was watching it happen in real-time to the technologies he cared about.
Fast forward to 2024. Microsoft loves Linux. Microsoft loves open source. Microsoft has a GitHub profile with a little heart emoji. And if you point out the pattern, you get called a conspiracy theorist.
The thing about trojan horses is that they don’t look like threats. They look like gifts.
Let’s walk through what’s actually happening, because the details matter more than the vibes.
Microsoft bought GitHub. Not because they wanted to support developers — because they wanted to own the pipeline through which all open-source code flows. Then they bought npm. Then they integrated everything into Azure. Then they made VS Code the default editor for an entire generation of programmers, ensuring that the tools you use every day are shaped by a company whose entire business model depends on you renting compute from them.
And here’s where it gets uncomfortable: Kubernetes runs on Azure. Linux runs on Azure. Your AI frameworks — PyTorch, ONNX, half the models on Hugging Face — they’re all being optimized, packaged, and deployed through Microsoft-controlled infrastructure. The open-source label stays on the box. The lock-in happens underneath.
Open source was supposed to be the escape hatch. Microsoft turned it into the front door — and they’re holding the key.
Now, the counterargument: “But Microsoft contributes to Linux! They’re one of the top kernel contributors!” True. And that’s precisely the point. When you’re the one writing the code, you’re the one deciding which features ship, which bugs get prioritized, and which integrations work best with your cloud. Contribution isn’t charity. It’s influence.
This is the same playbook, just with better PR. In the ’90s, Microsoft embraced Java, extended it with Windows-specific libraries (J++), and tried to extinguish cross-platform compatibility. Sun Microsystems sued them and won. But the lesson Microsoft learned wasn’t “don’t do this” — it was “do it slower, and buy the things you can’t control.”
So they bought LinkedIn. They bought GitHub. They bought Activision. They invested billions in OpenAI — not out of generosity, but because whoever controls the model layer controls the next decade of computing. And they’re wrapping all of it in an open-source-friendly bow so that no one sounds the alarm until it’s too late.
You don’t need to ban open source. You just need to own the infrastructure it runs on, the tools that build it, and the models that consume it. That’s not extinguishing — that’s absorbing.
If you’re a developer reading this, you’re probably already in the ecosystem. Your repos are on GitHub. Your containers run on Azure. Your IDE is VS Code. Your CI/CD pipeline goes through Microsoft-owned services. Each individual choice felt reasonable. Collectively, you’ve handed the keys to one company.
And that’s the genius of it. Microsoft didn’t force anyone. They made each step feel like a convenience. They made the proprietary path the path of least resistance. They didn’t extinguish open source — they domesticated it.
Torvalds saw this coming because he’d already lived through it. The question isn’t whether Microsoft’s strategy is real. The question is whether anyone will notice before it’s complete.
The most effective monopoly isn’t the one that blocks the exits. It’s the one that makes you forget there were ever exits at all.
So what do you do? You don’t need to panic-delete your GitHub account. But you do need to stop treating Microsoft’s open-source embrace as evidence of good faith. Treat it as what it is: a strategy. A very, very effective one.
Keep your options open. Self-host where it matters. Support independent infrastructure. And for the love of everything Linus built — read the history before you trust the present.
FAQ
Q: Isn't Microsoft genuinely contributing to open source now? Aren't they a top Linux kernel contributor?
A: Yes — and that's the problem, not the defense. When you write the code, you set the priorities. Contribution is influence. Microsoft isn't writing kernel patches out of generosity; they're shaping Linux to run best on Azure. The question isn't whether they contribute. It's whether they'd contribute if it didn't serve their cloud business.
Q: What does this mean for me if I'm already using GitHub, VS Code, and Azure?
A: You don't need to panic-migrate everything tomorrow. But you need to stop treating each Microsoft tool as an isolated, neutral choice and start seeing the aggregate. Self-host your critical repos. Evaluate alternatives for at least one layer of your stack. The goal isn't purity — it's optionality. Once you lose the ability to leave, the price goes up.
Q: Isn't this just anti-Microsoft bias? Google and Amazon do the same thing.
A: Google and Amazon absolutely play similar games — but Microsoft is uniquely dangerous because they own the developer workflow end-to-end: the editor (VS Code), the repository (GitHub), the package manager (npm), the cloud (Azure), and increasingly the AI layer (OpenAI partnership). No other company has that level of full-stack control over how software gets written, shared, and deployed. Calling that out isn't bias. It's pattern recognition.