this post was submitted on 04 Jun 2025
681 points (93.3% liked)
Programmer Humor
23844 readers
2457 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You are allowed wtf. If the plugin author didn't distribute it elsewhere, it's on them. MS doesn't forbid them from uploading the extension build elsewhere, they just wanted their marketplace not getting requests from not-their-client which is a fair point for a for profit company.
No. If you're using something other than Visual Studio Code you have to manually download plugins and the MS specific ones use licenses like this.
https://marketplace.visualstudio.com/items/ms-vscode.cpptools/license
Look at the usages of "In-Scope Products and Services" in Visual Studio Marketplace's Terms of Service. https://cdn.vsassets.io/v/M253_20250303.9/_content/Microsoft-Visual-Studio-Marketplace-Terms-of-Use.pdf
Then specify MS plugins. If you only said plugins on MS marketplace, you are blaming MS for things they didn't do
My use of "their" may have been too ambiguous. I thought it was clear from the context that I was talking about Microsoft's program, marketplace, and plugins specifically. When you use VS Code with things like C it's like "hey, download this extension!" So from your perspective that's a thing VS Code can do, because it's so seamless and easy to add in. But what you don't realize is that you're downloading a proprietary, closed source extension. When you use VS Codium you can't (easily) get those extensions (without breaking Microsoft's terms of service). It's the same shit that Oracle pulls with their JDK distribution and a big part of why OpenJDK usage is much more common post 2019ish.
Yes, hence why I commented that MS never prohibits you from publishing your extension elsewhere. Nor does MS forbid you from using other marketplaces when using their product. It's like saying valve is prohibiting game dev from publishing their game elsewhere or distributing their game outside of steam. It's just not true. And MS has all the right to limit their marketplace to their own client too. After all, it is first and foremost, their service for their product specifically. It's like you're making an unofficial client for youtube.
I never said MS is doing any of those things. I even linked their TOS to show you very clearly what they're doing and not doing.
I never said they shouldn't "have the right", I said they're open-washing. They act like VS Code is open source but the build they distribute is not and a lot of the functionality they add in through recommended plugins are both not open source and you're not allowed to easily download them from other plugins. Everything about VS Code is fauxpen source to the max.