Microsoft Blocks C/C++ Extension on VS Codium
- Microsoft's recent decision to limit the use of its popular C/C++ extension for visual Studio Code has triggered a wave of discontent among developers who rely on option...
- The change, technically an integrated control introduced in version 1.24.5 on April 3, effectively blocks the installation of the C/C++ extension in non-Microsoft products.While licensing restrictions have been...
- Cursor, a commercial code editor with integrated artificial intelligence built upon VS Code, has been directly affected.
Microsoft Restricts C/C++ Extension, Sparking Developer outcry
Microsoft’s recent decision to limit the use of its popular C/C++ extension for visual Studio Code has triggered a wave of discontent among developers who rely on option code editors. The restriction, implemented in an April update, prevents the extension from functioning in environments such as Cursor adn VS Codium.
Extension Lockout Impacts Alternative Editors
The change, technically an integrated control introduced in version 1.24.5 on April 3, effectively blocks the installation of the C/C++ extension in non-Microsoft products.While licensing restrictions have been in place as 2020, Microsoft had not previously enforced them for this particular extension, creating an obstacle for developers working outside the VS Code ecosystem.
Cursor Developers Seek Alternatives
Cursor, a commercial code editor with integrated artificial intelligence built upon VS Code, has been directly affected. The growth team, Anysphere, has already implemented a temporary workaround and plans to transition to alternative open-source extensions. Michael Truell, a co-founder of Cursor, stated the company’s intention to wholly eliminate dependencies on Microsoft’s proprietary extensions in the future.
Cursor’s Workaround and VS Codium’s Approach
Cursor reportedly circumvented the initial restrictions by using an inverse proxy to mask its requests to the Visual studio Marketplace, allowing it to download the official Microsoft extensions despite the imposed ban. In contrast, many VS Code forks, such as VS Codium, utilize Open VSX, an independent plugin repository.
FTC Complaint Alleging Anti-Competitive Practices
Amidst the technical discussions, some developers suspect ulterior motives behind Microsoft’s actions.One anonymous developer claimed to have filed a complaint with the Federal Trade Commission (FTC) in the United States. The complaint alleges that Microsoft is leveraging its dominant market position to promote its Copilot product, while simultaneously hindering competitors like Cursor by restricting access to essential extensions.
Concerns Over Microsoft’s Broader Strategy
Some developers point out that Microsoft has historically restricted the use of other proprietary extensions,including Pylance and Remote Access,to its own VS Code habitat. The submission of this policy to the C/C++ extension is seen as a notable blow to independent editors, particularly those that rely on the VS Code ecosystem to develop their features.
AI Assistant Competition Heats up
Adding fuel to the fire, Microsoft recently launched Agent Mode, an AI-powered coding assistant that directly competes with Cursor’s capabilities. Some developers believe that Microsoft’s aggressive defense of its extensions, coupled with the promotion of its new AI product, suggests an attempt to stifle growing competition in the code editor market.
Microsoft Restricts C/C++ Extension, Sparking Developer Outcry
What is the Microsoft C/C++ Extension Restriction?
Microsoft has implemented a new restriction, starting April 3, within its C/C++ extension for Visual Studio Code (VS Code). This change prevents the extension from being installed in non-Microsoft products. While some licensing restrictions have existed since 2020, this is the first time Microsoft has strictly enforced these limitations on this particular extension.
Why is Microsoft Blocking the C/C++ Extension?
The exact reasons aren’t explicitly stated in the provided text, but developers suspect anti-competitive practices. The change likely aims to encourage users to stick wiht Microsoft’s VS Code ecosystem, especially given the launch of their competing AI-powered coding assistant, Agent Mode.
which Code Editors Are Impacted?
Several code editors and developer environments are directly affected:
- Cursor: A commercial code editor that relies on the VS Code ecosystem, including Microsoft’s extensions.
- VS Codium: A VS Code fork that utilizes Open VSX, an autonomous plugin repository.
How is Cursor dealing with the Extension Lockout?
Cursor has implemented a temporary workaround. They are using an inverse proxy to mask their requests to the Visual Studio Marketplace, allowing them to download the official Microsoft extensions. However, Cursor plans to transition to alternative open-source extensions to eliminate dependencies on Microsoft’s proprietary tools in the future.
What is an Open VSX Registry?
Open VSX is an independent plugin repository. VS Codium uses this to access plugins, avoiding reliance on Microsoft’s marketplace.
Has Microsoft Restricted Other Extensions?
Yes, the article mentions that Microsoft has historically restricted the use of other proprietary extensions, including Pylance and Remote Access, to its own VS Code ecosystem.
What is the FTC Complaint About?
An anonymous developer filed a complaint with the Federal Trade Commission (FTC) alleging that Microsoft is leveraging its dominant market position to promote its Copilot product. The complaint claims Microsoft is hindering competitors like Cursor by restricting access to essential extensions,creating an unfair competitive advantage.
How Does AI Competition Play a Role?
Microsoft recently launched Agent Mode, an AI-powered coding assistant similar to Cursor’s features. Some developers believe this, coupled with the restriction on the C/C++ extension, suggests an attempt to stifle competition in the code editor market by protecting its new AI product.
Summary of Key Differences in Approaches
A table summarizing the key differences between the affected editors can be seen below:
| Feature | Cursor | VS Codium |
|---|---|---|
| Dependency on microsoft Extensions | Initially reliant, implementing a temporary workaround, and planning to move to alternatives. | Avoids direct reliance, using the Open VSX registry. |
| Approach to Extension Access | Uses an inverse proxy to bypass restrictions by masking requests to the Visual Studio Marketplace. | Uses the Open VSX registry,an independent plugin repository. |
| Goal | Remain competitive while reducing reliance on Microsoft’s proprietary extensions. | Maintain open access to code editing tools. |