If you're like me and you've been happily using VSCodium (or maybe even Cursor, that cool AI editor) for your C/C++ projects, you might have hit a snag recently. Microsoft, in their infinite wisdom, decided to start enforcing the license terms on their official C/C++ extension for VS Code.
#What's the Big Deal?
For a long time, even though the C/C++ extension wasn't officially in the VSCodium marketplace, we could just grab the .vsix file from Microsoft's GitHub and install it manually. It was a bit of a hoop to jump through, but hey, it worked! We got all those sweet IntelliSense and debugging features without the Microsoft telemetry.
But with the latest version (1.24.5), that's over. Try to use it on VSCodium now, and you'll get a "nope, this is for official Microsoft products only" message.
#Why the Sudden Change?
I wonder if it's related to tools like Cursor getting popular, maybe stepping on some AI toes. Microsoft says they're just enforcing terms that were always there. Their response to user complaints on the marketplace has been a bit... well, corporate: "Sorry you're upset we're enforcing our rules."
It's a bit frustrating because, while the extension source code is MIT licensed, the binaries we download have always had this more restrictive license. They just didn't bother checking until now.
#So, What Now?
If you're stuck on VSCodium and need C/C++ support, you do have options. You can roll back to an older version of the extension (pre-1.24.5) and disable auto-updates. That's not ideal since you'll miss out on bug fixes and new features, but it keeps you working.
Another option is switching to clangd. It's an alternative language server that works well with C and C++ code. It's not a perfect drop-in replacement for the Microsoft extension, but for a lot of projects, it does the job just fine. Plus, it's fully open source and works on any editor that supports the Language Server Protocol.
You could also just... use VS Code. I know, that kind of defeats the purpose if you switched to VSCodium to avoid Microsoft's telemetry in the first place. But if the C/C++ extension is critical to your workflow, it might be the path of least resistance.
#The Bigger Picture
This whole situation is a good reminder of something that's easy to forget. Even when a project is technically open source, the ecosystem around it can be a different story.
VS Code itself is MIT licensed. You can fork it, modify it, redistribute it. That's why VSCodium exists in the first place. But Microsoft also builds and maintains a lot of the most popular extensions, and those have their own licenses. The C/C++ extension is a prime example. The source is open, but the prebuilt binaries they ship through the marketplace? Those come with restrictions.
It's a clever move when you think about it. Keep the core open to build adoption and community goodwill, but lock down the pieces that developers actually depend on day to day. Not saying it's evil or anything, just something to be aware of when you're choosing your tools.
For now, I'll probably stick with VSCodium and give clangd a shot for my C projects. It's a bit of a hassle, but I like knowing exactly what's running on my machine. Your mileage may vary.