Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, open-source dynamics, and the evolving landscape of development tools.
What This Article Covers
This article delves into a significant move by Microsoft that impacted the compatibility of its VSCode extension with a competing platform, Cursor. It explores the implications of this change, the history behind Microsoft's strategic maneuvers with open standards, and how this recent development fits into a larger pattern of behavior.
Questions This Article Answers
- What specific change did Microsoft make to its VSCode extension that affected Cursor?
- How does Microsoft's action relate to the "embrace, extend, extinguish" strategy?
- What are the potential consequences for developers using VSCode forks?
- How widespread is the impact of this change across Microsoft's other extensions?
- What alternative options are available for developers affected by this restriction?
Length and Time
A comprehensive exploration of recent changes in VSCode extension policies with historical context. Approximately 10 minutes to read.