3 ms·
There is an alternative public directory: https://open-vsx.org/ https://open-vsx.org/ It's used by vs codium and theia. It's not just those two plugins, it's
by swsieber 6y ago
There is an alternative public directory: https://open-vsx.org/ https://open-vsx.org/
It's used by vs codium and theia.
It's not just those two plugins, it's also the ms-code.cpptools which has proprietary parts. And that's sad because other plugins are built on it like platformio. Which prevents platformio from being added to ovsx because the cpp tools can't be added to ovsx.
Which stinks for me because the cpp proprietary parts are windows only, and all I want to use platformio from is theia running on Linux, but I can't.
VS Codium: https://github.com/VSCodium/vscodium https://github.com/VSCodium/vscodium
Theia IDE: https://theia-ide.org/ https://theia-ide.org/
More details about PlatformIO not being to be added to OVSX: https://github.com/open-vsx/publish-extensions/issues/86 https://github.com/open-vsx/publish-extensions/issues/86
More cpp tools licensing details: https://github.com/microsoft/vscode-cpptools/issues/5784 https://github.com/microsoft/vscode-cpptools/issues/5784
Edit: you can run theia from one computer and use it via the browser on another. That's why I was so excited for it.
Edit 2: VS Codium, not open codium
- pythonaut_16 6y agoThe other side is that keeping some extensions closed-source probably allows the VS Code team to access more of Microsoft's work. I would guess that the proprietary parts of ms-code.cpptools are using code from Visual Studio and other closed-source Microsoft tooling.
- swsieber 6y agoOh, definitely. I understand it. It's just sad for me, personally, since I don't use those parts but it blocks other things (cpp dependent) plugins.