[Ontonator]

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

[Karliss]

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.

[sschueller]

There is a workaround for PlatformIO that I use to get it to work in VSCodium: https://github.com/platformio/platformio-vscode-ide/issues/1...

[IshKebab]

Not sure about C++ but the Python extension definitely isn't completely open source. That code appears to be for the extension client, but the code for Pylance isn't open (which provides completions etc.). The code for Pyright (the type checker) is open source though.

https://github.com/microsoft/pylance-release/issues/4#issuec...

[tristan957]

Really makes you wonder what Microsoft gains keeping this stuff in their closed-source bubble.