Microsoft, Codeven, and Red Hat announce open source Language Server Protocol (LSP) for IDEs
Codenvy, Microsoft, and Red Hat have announced they are adopting a universal Language Server Protocol for integrated development environments. — Microsoft — yes, Microsoft …
Context & Ripple Effects
The Language Server Protocol announcement is another rung in Microsoft's multi-year climb toward openness with its developer tools: the company had already opened up its Visual Studio Code editor and added Linux debugging and partnered with Red Hat to bring Linux to Azure.
What makes this one structurally different is that Microsoft is not just releasing its own code — it is co-authoring a vendor-neutral standard with Codenvy and Red Hat that decouples language intelligence from any single editor, weeks before it would go on to open source PowerShell for Linux and OS X.
First-order effects
- Editor and IDE makers can now add rich language support by implementing one protocol instead of writing a bespoke integration per language, with Microsoft, Red Hat, and Codenvy as the reference adopters.
- Red Hat and Codenvy gain standing in developer tooling they could not have bought: their names sit alongside Microsoft's on a spec that Microsoft's own editor will speak.
Second-order effects
- Language-tooling vendors get distribution across every conforming editor at once, shifting competitive pressure from who integrates with whom to whose language server is best — and undercutting the moat of closed ecosystems like Visual Studio proper.
- Rival IDE vendors face a choice between adopting a Microsoft-co-authored standard or maintaining expensive proprietary integrations, a dynamic familiar from Microsoft's earlier Azure-overtures to Red Hat.
Third-order effects
- If language intelligence lives behind a protocol rather than inside an editor, the editor itself becomes replaceable — the precondition for the browser-based, collaboration-first direction Microsoft later took with Visual Studio Online built on VS Code and shared-cursor editing via Live Share.
- The pattern points toward development environments consolidating around open protocols and cloud services, with the spec's stewards — not the editor vendors — holding the durable position.
The trend: Developer tooling is reorganizing around open, editor-agnostic protocols, letting Microsoft convert its once-closed IDE franchise into standards and cloud services leadership.