Summary

Microsoft presented comprehensive open-source tools at Build 2026: an open-source AI terminal, WSL containers, and over 75 Unix tools. The company is also embracing open standards such as PostgreSQL instead of proprietary databases. This development marks a strategic shift: Microsoft's historical tactic of "Embrace, Extend, Extinguish" (EEE) – stifling open standards – no longer works. The business model has shifted from licensed software to cloud platform services.

People

Topics

  • Cloud computing and business models
  • Open-source software and proprietary standards
  • Microsoft strategy and competition
  • Developer tools and platform services

Clarus Lead

Microsoft's embrace of open source is not capitulation, but a calculated business decision. The cash register is no longer at the system boundary (Windows vs. Linux), but at the cloud service – Azure, GitHub, and Copilot foot the bill. While developers celebrate the new free tools, the industry continues to centralize around a single provider. Ballmer's admission that the earlier hard line lies "in the rear-view mirror" reveals the sober logic: first fight, then cash in, finally embrace.

Detailed Summary

Microsoft's historical EEE strategy is documented. The U.S. Department of Justice investigated how the company infiltrated open markets, extended standards through proprietary features, and excluded competitors. In the browser war against Netscape, internal memos showed that Microsoft intended to deliberately intertwine Office and HTML to strengthen only its own ecosystem.

The current strategy is fundamentally different: the third "E" (Extinguish) is missing. With everyday developer tools, Microsoft yields no ground – no one has to migrate, no open standard leads into a proprietary dead end. The friction only costs development effort, not market power. Azure HorizonDB builds on PostgreSQL and positions AI services around it, rather than forcing a closed database.

The shift began in 2014 under Nadella: from license sales to monthly rentals. Over half of Azure workloads run under Linux – part of the business model, not a loss. Ballmer confirms in retrospect that the earlier stance was economically correct at the time, but Linux concerns belong to the past.

Trust remains justifiably tense: in 2021, Microsoft attempted to isolate Hot-Reload from open-source .NET and only backed down after protests. Tools like GitHub, Copilot, and Codespaces carry proprietary layers – each use further centralizes. Microsoft's open-source affection may be genuine, but it springs not from altruism but from the calculation of not stagnating like IBM. In five years, different business logic may apply.

Key Statements

  • Microsoft has abandoned the EEE strategy because the cloud business model requires different revenue sources
  • Open source is no longer a contradiction to profit, but its foundation
  • The industry continues to centralize around a single provider despite open tools
  • Developer trust remains justifiably skeptical of proprietary layers

Critical Questions

  1. Evidence: How does the U.S. Department of Justice specifically document EEE practices, and are the browser war memos authentically verified?

  2. Conflicts of Interest: To what extent does Microsoft's open-source adoption serve market consolidation rather than genuine decentralization – in other words: is openness a means to platform dependency?

  3. Causality: Is the strategic shift driven primarily by cloud business logic or by competitive pressure (Google, Amazon)?

  4. Feasibility: How quickly can Microsoft re-impose proprietary layers (GitHub, Copilot) if the cloud model comes under pressure?

  5. Data Quality: What share of Azure workloads under Linux is current, and how is this measured?

  6. Counter-Hypotheses: Could Microsoft's open-source engagement also correspond to genuine security or stability requirements, not just business considerations?

  7. Risks: How does the market react if proprietary services (Copilot, GitHub) raise prices and decouple open tools?

  8. Side Effects: Which smaller open-source projects lose competitiveness due to Microsoft's resource advantage?

Source List

Primary Source: Förster, Moritz (2026): "Commentary: Microsoft's Open-Source Love Has a Price" – https://www.heise.de/meinung/Kommentar-Microsofts-Open-Source-Liebe-hat-einen-Preis-11320098.html

Supplementary Context:

  • Microsoft Build 2026 (announcements on AI terminal, WSL, Coreutils)
  • U.S. Department of Justice documentation (EEE strategy)
  • Azure PostgreSQL/HorizonDB initiative

Verification Status: ✓ 2026

This text was created with the support of an AI model. Editorial responsibility: clarus.news | Fact-checking: 2026