AI summary by TwinMind
Microsoft Cracks Down On VS Code Forks
Theo - t3․gg
38m 46s
Background: Evolution of Code Editors
- Sublime Text started minimal extensible editor revolution
- Community-driven marketplace, free to use, fast, minimal
- Not open source, paid editor with popup every 20 saves
- Built foundation for community extensibility concept
- GitHub created Atom as open source alternative
- Built on Electron (invented for Atom distribution)
- Fully free/open source, JavaScript-based extensions
- Slower than Sublime, missing traditional IDE features
- Poor startup times, less polished experience
- Microsoft developed VS Code as response
- Visual Studio team recognized community shift toward minimal editors
- Positioned as "Visual Studio for webdevs"
- Built on Electron, community extensible, fully free/open source
- Better performance than Atom, strong TypeScript integration
- TypeScript success drove initial VS Code adoption
- Eventually led to Atom being deprecated/shut down
Current Extension Restriction Issue
- April 2025: Users seeing error blocking Microsoft extensions in non-MS editors
- C++ extension: "may only be used within Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps"
- Also affects .NET and other Microsoft extensions
- Impacts Cursor, Windsurf, and other VS Code forks
- Problem particularly affects C++ developers using Cursor
- Basic syntax highlighting and language features broken
- Install specific version dropdown also removed
- Workarounds involve downgrading to older extension versions
Cursor's Technical Evolution Timeline
- April 2023: Cursor moved from CodeMirror to VS Code base
- September 2023: Cursor introduced "Cursor marketplace"
- Speculation: Likely wrapper around official VS Code marketplace
- Previously used Open VSX marketplace from Eclipse
- November 2024: Cursor marketplace switched back to Open VSX
- Official Microsoft extensions no longer searchable in editor
- Published guide: "How to install any VS Code extension in Cursor"
- Most Cursor users imported extensions from existing VS Code setups
- Didn't encounter marketplace issues initially
- Extensions likely outdated but users unaware
Microsoft's Terms of Service Changes
- 2021 VS Code marketplace terms: Vague restrictions on scraping/harvesting
- January 2025: Much stricter terms published
- "You may not import, install, or use offerings published by Microsoft or GitHub or Microsoft affiliates in any product or services except for the in-scope products and services"
- Very explicit callout targeting wrapper implementations
- February 2025: Microsoft removed download button from browser marketplace
- Official reason: Issues with pre-release vs stable version downloads
- Made manual extension installation much harder
- Cursor's installation guide became obsolete
Extension Licensing Complexity
- Many Microsoft extensions have confusing dual licensing
- Source code: MIT licensed
- Binary runtime components: Microsoft proprietary license
- Easy to misunderstand actual usage restrictions
- .NET extension requires paid Visual Studio subscription
- Paying customers now blocked from using in alternative editors
- C++ extension: Source available but not truly open source
- Runtime components under restrictive proprietary licenses
Author's Conspiracy Theory Assessment
- Believes restrictions result from 3 separate team decisions, not coordinated attack:
- Download button removal: Technical fix for version branching issues
- Extension restrictions: Language teams tired of bug reports from outdated forks
- VS Code agent mode: Competitive response to Cursor's AI features
- Microsoft teams likely getting support burden from fork users
- Forks based on 2-year-old VS Code versions
- Important improvements may not be backported to forks
- Results in compatibility issues and bug reports
- Analogy: Author's own experience blocking Brave browser due to reCAPTCHA issues
- Single browser causing disproportionate support burden
- Similar to .NET team potentially blocking problematic forks
VS Code's Strategic Purpose
- Never intended as revenue generator for Microsoft
- Part of developer sentiment improvement strategy
- Similar to TypeScript: improve dev experience and reputation
- First good cross-platform editor from Microsoft
- Goal: Make developers love Microsoft again
- Position for future revenue opportunities
- Not direct monetization of editor itself
Future Implications and Predictions
- VS Code forks will adapt through:
- Better import workflows from VS Code
- Encouraging developers to publish on Open VSX marketplace
- Development of open alternatives to proprietary language runtimes
- .NET development particularly impacted
- .NET developers frustrated by Cursor restrictions
- Unlikely to see good .NET experience in Cursor going forward
- Microsoft unlikely to pursue aggressive legal action
- Would damage developer relations they've worked to rebuild
- Bad optics similar to historical Netscape lawsuit
- Open source alternatives to proprietary components likely to emerge
