5 ms·

If I switch from VS Code to VSCodium, will I notice anything different - assuming the telemetry is not really visible to me and I ignore the branding? Will the

If I switch from VS Code to VSCodium, will I notice anything different - assuming the telemetry is not really visible to me and I ignore the branding? Will the plugins - some provided by MS - still work as expected or will those be blocked or hobbled? Thanks!

wheelerof4te 3y ago
> Will the plugins - some provided by MS - still work as expected or will those be blocked or hobbled? Nope. Only some.
- trelane 3y ago
  What about the other way: will plugins designed for VSCodium work in VSCode?
  - ReleaseCandidat 3y ago
    There is no such thing as "designed for VSCodium". You can publish your extension on Open VSX only instead of in the MS Marketplace.
    - trelane 3y ago
      > You can publish your extension on Open VSX only instead of in the MS Marketplace. So to use an extension in VSCode, it has to be published in Microsoft's store? And VSCode only in this other store?
      - ReleaseCandidat 3y ago
        > So to use an extension in VSCode, it has to be published in Microsoft's store? You can always download the extension (or build it yourself) and install it manually - using Code or Codium. You can use the Open VSX registry with Code, but you have to configure it: https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS.... So it technically does not have to be in MS' Marketplace, but 99% of Code user will not find or know of your extension, if it isn't in the Marketplace.
hooverd 3y ago
Pylance won't. There's the EEE you're looking for.
- codethief 3y ago
  IIRC there was a ticket somewhere in the issue tracker where someone explained in the comments how to get Pylance to work. Wasn't particularly difficult.
  - hooverd 3y ago
    For now. Who knows how long it be before it only runs against a signed Microsoft VSCode binary?
  - CameronNemo 3y ago
    Just use the open source python LSP that is written in Python and maintained by the Spyder IDE team. https://github.com/python-lsp/python-lsp-server https://github.com/python-lsp/python-lsp-server Someone might come along and tell you that you are missing out on some pylance features, but fuck closed source dev tooling it ain't worth it.
BossingAround 3y ago
From my experience, the UI is very slightly different, with some options/functionality missing here and there (from what I remember, for example, you couldn't enlarge the font size of the menus). The plugins won't work out of the gate, but you can installed them manually and most of them will work. It's not a 1:1 replacement, and from my limited experience, the UX of VSCodium was worse than that of VSCode. But, if you value not being tied to MS... That's the price you're gonna pay.
- hedora 3y ago
  Are you sure you weren’t using an older version of one? I see no practical difference between code on macos and vscodium on Linux (except that I prefer Linux’s font renderer, and the ctrl key moved).
codethief 3y ago
In my experience all extensions will work & will be installable right from the in-app marketplace, provided that you follow https://news.ycombinator.com/item?id=37382473 https://news.ycombinator.com/item?id=37382473 There was a ticket somewhere in the issue tracker with more information about this topic.
replete 3y ago
I switched to vscodium two years ago and I haven't had any problems
whalesalad 3y ago
Remote SSH dev does not work.
- jeanp413 3y ago
  There's https://open-vsx.org/extension/jeanp413/open-remote-ssh https://open-vsx.org/extension/jeanp413/open-remote-ssh it works in most cases
  - hedora 3y ago
    I’m using that, and haven’t noticed any differences between vscodium and the closed source one (other than the removal of telemetry).
  - ranguna 3y ago
    Unfortunately that one doesn't support hardware keys unfortunately

wheelerof4te 3y ago

> Will the plugins - some provided by MS - still work as expected or will those be blocked or hobbled? Nope. Only some.

trelane 3y ago
What about the other way: will plugins designed for VSCodium work in VSCode?
- ReleaseCandidat 3y ago
  There is no such thing as "designed for VSCodium". You can publish your extension on Open VSX only instead of in the MS Marketplace.
  - trelane 3y ago
    > You can publish your extension on Open VSX only instead of in the MS Marketplace. So to use an extension in VSCode, it has to be published in Microsoft's store? And VSCode only in this other store?
    - ReleaseCandidat 3y ago
      > So to use an extension in VSCode, it has to be published in Microsoft's store? You can always download the extension (or build it yourself) and install it manually - using Code or Codium. You can use the Open VSX registry with Code, but you have to configure it: https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS-Code https://github.com/eclipse/openvsx/wiki/Using-Open-VSX-in-VS.... So it technically does not have to be in MS' Marketplace, but 99% of Code user will not find or know of your extension, if it isn't in the Marketplace.

hooverd 3y ago

Pylance won't. There's the EEE you're looking for.

codethief 3y ago
IIRC there was a ticket somewhere in the issue tracker where someone explained in the comments how to get Pylance to work. Wasn't particularly difficult.
- hooverd 3y ago
  For now. Who knows how long it be before it only runs against a signed Microsoft VSCode binary?
- CameronNemo 3y ago
  Just use the open source python LSP that is written in Python and maintained by the Spyder IDE team. https://github.com/python-lsp/python-lsp-server https://github.com/python-lsp/python-lsp-server Someone might come along and tell you that you are missing out on some pylance features, but fuck closed source dev tooling it ain't worth it.

BossingAround 3y ago

From my experience, the UI is very slightly different, with some options/functionality missing here and there (from what I remember, for example, you couldn't enlarge the font size of the menus). The plugins won't work out of the gate, but you can installed them manually and most of them will work. It's not a 1:1 replacement, and from my limited experience, the UX of VSCodium was worse than that of VSCode. But, if you value not being tied to MS... That's the price you're gonna pay.

hedora 3y ago
Are you sure you weren’t using an older version of one? I see no practical difference between code on macos and vscodium on Linux (except that I prefer Linux’s font renderer, and the ctrl key moved).

codethief 3y ago

In my experience all extensions will work & will be installable right from the in-app marketplace, provided that you follow https://news.ycombinator.com/item?id=37382473 https://news.ycombinator.com/item?id=37382473 There was a ticket somewhere in the issue tracker with more information about this topic.

replete 3y ago

I switched to vscodium two years ago and I haven't had any problems

whalesalad 3y ago

Remote SSH dev does not work.

jeanp413 3y ago
There's https://open-vsx.org/extension/jeanp413/open-remote-ssh https://open-vsx.org/extension/jeanp413/open-remote-ssh it works in most cases
- hedora 3y ago
  I’m using that, and haven’t noticed any differences between vscodium and the closed source one (other than the removal of telemetry).
- ranguna 3y ago
  Unfortunately that one doesn't support hardware keys unfortunately