Tooling Lock-InNarrow moat

From the center that GitHub provides, tooling lock-in radiates outward. The editors, the languages, the frameworks, and the cloud services a developer reaches for without conscious thought are increasingly Microsoft's — Visual Studio Code above all, the free editor that became the most widely used development tool in the world — and each one makes the next Microsoft product a more natural choice. When the tool you build with, the place you store your code, and the cloud you deploy to all come from one vendor and fit together, the friction of choosing anything else quietly rises with every project.

The strategic subtlety is that these tools need not be profitable in themselves, so long as they steer what gets built toward the products that are. A free editor, a welcoming language, an open-source framework given away at cost — each is bait that leads, in time, to a paid cloud, a paid subscription, a paid service. Microsoft learned to treat the developer not as a small customer to be charged but as the gatekeeper to every future customer.

The lock-in works through habit and fit rather than contract. A developer fluent in VS Code, comfortable with TypeScript, deploying to Azure out of muscle memory, is bound by no agreement — but the accumulated familiarity and the seamless integration make the Microsoft path the one of least resistance, and least resistance is what developers, busy and pragmatic, usually choose.

For the owner, tooling lock-in is the mechanism that converts the GitHub high ground into durable advantage: it shapes the daily choices of millions of developers toward Microsoft's paid platforms, quietly and continuously, by being the easiest thing to reach for. It is a moat made of a thousand defaults, radiating from a GitHub that hosts most of the world's code¹.