It also plays into their goal to make VS Code seem open source while being the opposite! A lot of the functionality is in the marketplace but non Microsoft products aren't legally allowed to use it and you're not allowed to distribute builds of the plugins.

Use VS Codium instead.

[–] bitfucker@programming.dev 1 points 11 hours ago (1 children)

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.

[–] JackbyDev@programming.dev 2 points 10 hours ago* (last edited 10 hours ago) (2 children)

You are allowed wtf.

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

SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. For clarification Microsoft, or its licensors, retains ownership of all aspects of the software. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. For example, if Microsoft technically limits or disables extensibility for the software, you may not extend the software by, among other things, loading or injecting into the software any non-Microsoft add-ins, macros, or packages; modifying the software registry settings; or adding features or functionality equivalent to that found in Microsoft products and services. You may not: a) work around any technical limitations in the software that only allow you to use it in certain ways; b) reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; c) remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; d) use the software in any way that is against the law or to create or propagate malware; or e) share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.

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

[–] bitfucker@programming.dev 1 points 10 hours ago (1 children)

Then specify MS plugins. If you only said plugins on MS marketplace, you are blaming MS for things they didn't do

[–] JackbyDev@programming.dev 1 points 1 hour ago* (last edited 1 minute ago)

It also plays into [Microsoft's] goal to make VS Code seem open source while being the opposite! A lot of the functionality is in the marketplace but non Microsoft products aren't legally allowed to use it and you're not allowed to distribute builds of the plugins.

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.

[–] rikudou@lemmings.world 6 points 1 day ago

Well, IntelliJ is also plugin based, it's just that most of the plugins are bundled and enabled by default and maintained by the same set of people as the core IDE, so there's consistent quality.