3 ms·
I went backwards, from VS Codium to VS Code, because VS Codium does not support all extensions, like PyLance or Remote - SSH/containers. I like freedom, but I
by wooque 4y ago
I went backwards, from VS Codium to VS Code, because VS Codium does not support all extensions, like PyLance or Remote - SSH/containers.
I like freedom, but I like getting things done more.
- bityard 4y agoI just did the same thing literally yesterday for the same reason. Disabled telemetry and hoping for the best.
- icelancer 4y agoI was considering switching and looking into Codium and then saw this comment. I'm not going without Remote-SSH or PyLance.
- Sujan 4y agoIt might be worth contacting these extensions' creators. If you already have the `.vsix` file for the VSCode marketplace, publishing to open-vsix is really super simple (create an account once, get a token, add a few lines to your publish script, e.g. https://github.com/prisma/language-tools/blob/94e4cd612d03ef84e3cac2acb041390f318ba907/.github/workflows/7_publish.yml#L106-L107 https://github.com/prisma/language-tools/blob/94e4cd612d03ef...). Some just do not know about it.
- cbarrick 4y agoPyLance and the remote extensions are developed by Microsoft. They intentionally do not work with the open source editor.
- Sujan 4y agoOh, I did not connect these dots. Shucks.
- whazor 4y agoHave you actually tried installing PyLance in VS Codium? I have not and also do not know if it works. But PyLance is available in https://open-vsx.org/extension/ms-python/python https://open-vsx.org/extension/ms-python/python and it seems there are no license issues.