vscode-cpptools

You are defending Microsoft. https://github.com/VSCodium/vscodium/blob/master/docs/extens... https://github.com/VSCodium/vscodium/blob/master/docs/extens... https://github.com/microsoft/vscode-cpptools/wiki/Microsoft-...

> I honestly don't remember when they tried to snare someone to use proprietary extensions to something open. Try using VSCodium legally with the same functionality as VSCode; remote development, Python language server, C++ debugging, and so on. People who think Microsoft is doing open source work for the good of their hearts are still in for a lesson in EEE. https://github.com/VSCodium/vscodium/blob/master/docs/extens... https://github.com/VSCodium/vscodium/blob/master/docs/extens... https://github.com/microsoft/vscode-cpptools/wiki/Microsoft-... https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

C++ modules still not supported on VSCode, always pissed when I get notifications from this 5 y.o. thread [0]. 0: https://github.com/microsoft/vscode-cpptools/issues/6302

How is it not open-source? It's licensed under MIT + VS Marketplace Terms: https://github.com/microsoft/vscode-cpptools?tab=License-1-o... If you fork it and don't use VS Marketplace, it's only MIT. Or am I missing something?

Assuming that you're referring to https://github.com/microsoft/vscode-cpptools/issues/6302, I see two comments along these lines, neither of which is from actual implementers. That isn't evidence either that the standard is a mess, nor that it's likely to go away. The reason why this is taking such a long time is because the entire approach is a rather drastic change to how C++ compilers usually work, and C++ compilers (or even frontends, such as the stuff used by IDEs) are complicated things that aren't trivial to make major changes to.

It's just disingenuous for Microsoft to say, for example, the cpptools extension is MIT licensed, which it is. https://github.com/microsoft/vscode-cpptools?tab=License-1-o... In reality, it's a MIT-licensed wrapper. The real license is also included in the repository, just not the top level github license. https://github.com/microsoft/vscode-cpptools/blob/main/Runti... The disingenuity is what you are condoning. The repo is superficially organized to appear open-source but is actually a minefield. Github will sometimes say "found other licenses"; the best Github can do is to "report" on the state of a repository; it's up to the community to decide on stricter tolerances for declaring something to be open-source, because as we see here, even a major corporation is willing to engage in subterfuge/exploitation. Saying something is "open sour

Its close in spirit to DRM: they enforce that if you are using their projects, it is under their legal terms. Many of their VS Code extensions[0] have license terms which /prohibit/ them from being used in editors that are not Microsoft's VS Code editor, and Microsoft can issue cease-and-desist for violations of this, as well as 'open source forks of VS Code' using their marketplace services. Microsoft also has a pattern they follow where they publish repositories on GitHub to proclaim they are open source, while actually distributing proprietary binary blobs in them that are fundamental core parts of functionality to the codebase[2][3][4] [0] https://github.com/microsoft/vscode-cpptools/issues/6388#iss... [1] https://github.com/microsoft/vscode-cpptools/issues/5784 [2] https://github.com/microsoft/win32metadata/issues/766 [3] https://dev

Here's a good comment thread from cpptools extension: https://github.com/microsoft/vscode-cpptools/discussions/126... Having not delved too deeply into building from source, this post suggests it's not even possible. We will need some new terminology to express that a given codebase is OSS licensed and the build dependencies additionally are OSS licensed.

The C/C++ extension is open source with MIT license but the shipped extension binary contains MS proprietary binaries that is not as open [1]. I am not sure what will be the difference between using MS official build and compiling the source (there will be some for sure). [1] https://github.com/microsoft/vscode-cpptools/blob/main/LICEN...

Now if only MS would fix VSCode[0] :'( .Come on, the feature if more than half a decade old and this point. 0: https://github.com/microsoft/vscode-cpptools/issues/6302

The actual repo seems MIT though https://github.com/microsoft/vscode-cpptools/blob/main/LICEN... ... what is missing from this?

> I'd love to see someone downvoting me provide a compelling response to the full source available here under the MIT license You are literally pointing to a github repo in order to respond to a complain about how MS makes github repos just to create the false appearence that their software is FLOSS. For example, the C/C++ parser also appears to claim to be "MIT" licensed if you go to the repository: https://github.com/microsoft/vscode-cpptools/blob/main/LICEN... However, it actually is not, by evidenced by the two line disclaimer at the beginning of that file. The entire thing is absolutely useless without the gigantic 100MB intellisense binary. Most definitely this does NOT rely on any functionality provided by "3rd party servers". It is entirely offline, 1st party code, that gets surreptitiously installed alongside the FLOSS "package"

While part of the C/C++ extension is MIT licensed. At runtime the extension downloads binary blobs which have a lot more restrictive license. See https://github.com/microsoft/vscode-cpptools/tree/main/Runti... . This effectively makes it illegal to use the extension in non official Visual Studio Code builds like VSCodium. The situation is similar with C# extension. There are alternative non Microsoft language servers for C++ and probably other languages which are fully open source and can be used in open source VSCode builds. But unfortunately some extensions depend specifically on the Microsoft language support extensions. For example Platform IO can't be published on OpenVSX due to this. https://github.com/platformio/platformio-vscode-ide/issues/1... . Similar with Unity debugger extension depending on microsoft C# extension.

Both the C/C++ and Python extensions seem to be open source, but I think you’re right about the remote development one. https://github.com/Microsoft/vscode-cpptools https://github.com/Microsoft/vscode-python