7 ms·

If anyone is interested in an experience report, I've been using it for about three years and it's exactly the same experience as VSCode (even works with Live S

by jxf 4y ago

If anyone is interested in an experience report, I've been using it for about three years and it's exactly the same experience as VSCode (even works with Live Share, for example). The main thing you'll have to contend with is that the extension registry for VSCode is different from Codium, as Geoff says here: https://news.ycombinator.com/item?id=31606704 https://news.ycombinator.com/item?id=31606704 This means you might find that extensions you use in VSCode aren't in Codium. This is usually remedied by just downloading the extension manually yourself or by asking the extension developers to cross-publish.

Cupprum 4y ago
Some Microsoft extensions do not work in vscodium. I have been using it for more than a year now, but i still miss the remote development using SSH.
- fartcannon 4y ago
  You get all that for free with a terminal in Linux. And KDE has all kinds of tools that remotely work with SSH. Dolphin can, for example, treats a remote SSH connection like a local file system.
  - hughw 4y ago
    How does a Linux terminal replicate the remote capability of VS Code?
    - pxc 4y ago
      What does the SSH capability let you do, exactly? Just edit remote files as if they were local?
      - jaywalk 4y ago
        It basically runs everything on the remote machine. So when you hit F5 to debug, the code is actually (transparently) running on the remote machine. It's pretty cool.
        fartcannon 4y ago
        Since KDE 3.5 (2002) you can use SSH to mount folders in the file manager and modify not just code remotely as if it was local, but other files too.
        jaywalk 4y ago
        Not even close to what this does. It basically runs a headless version of VSCode on the remote machine, with all of the necessary extensions, and your local version of VSCode controls it.
        fartcannon 4y ago
        When you SSH into something, you type, for example, 'vim' into the terminal, and then you're running the remote version of vim on that machine. If however, you want to use your local version of vim, you can do that too. With the previously mentioned kde tools. Is it something different than that?
        jamesgeck0 4y ago
        Yes, this is different. Vim is a TUI application which can easily run over vanilla SSH. VSCode is a GUI, which cannot. VSCode Remote runs the editor in a client/server mode, with all the UI running on the client and everything else seamlessly running on the server. There's none of the typical latency you get by running heavy operations such as full-text search on a mounted remote filesystem because they're run on the server.
        fartcannon 4y ago
        So, ssh -X? To me it sounds like a lot of needless bloat but cool, glad to learn a new thing.
        lights0123 4y ago
        That will run both the backend and the frontend on the remote server, while VS Code SSH will only run the backend on the remote. ssh -X is very slow for a complex GUI across a non-local network.
- runeks 4y ago
  > […] but i still miss the remote development using SSH Me too. Editing text is pretty light weight, so it makes sense to run locally. But the language server is often rather heavy weight, e.g. requires compiling all project dependencies, so it makes perfect sense to run this on a beefy remote machine (connected to wall power).
- jxf 4y ago
  Which Microsoft extension specifically is that? There are quite a few MS ones that have Codium equivalents which are effectively identical, though I don't use the one you're referring to.
kimbernator 4y ago
I used vscodium for a while up until this change was made. The maintainers changes the extension registry to the new one while it had something like 40 total extensions available without any sort of meaningful notification to users, and in a minor version release no less. Pretty shitty move, IMO. I have trouble trusting maintainers that are willing to push such drastic changes without letting people know.
- prophesi 4y ago
  By April 2020, it had roughly 200 extensions because there was no push for marketing it just yet. By the time VSCodium implemented it in June 2022, the push to move extensions over was in the works, and hundreds more were added. Also have been using VSCodium for years and the transition had no effect on my daily work, despite needing plugins on new machines for the relatively niche language of Elixir.
  - kimbernator 4y ago
    I'm sure it works fine now, and I don't doubt that it was fine in your case, but it was a huge inconvenience for me and the maintainers were pretty unhelpful about it when people complained. It literally took 9 months for a feature to be added that allowed changing the marketplace a user wanted without it being overwritten by updates. https://github.com/VSCodium/vscodium/issues/418 https://github.com/VSCodium/vscodium/issues/418 The correct way to do this would have been to start with a way to persistently change the marketplace URL being used and having the change be opt-in, then having a major version release when the default value was changed, including obvious instructions about how to change the desired marketplace. Instead, people were told to do the work themselves of porting over the extensions they wanted. That's a great way to get people who don't have the time or interest in that to just abandon the project altogether. Even if it is fine now, I just don't want a tool I use for my daily work to be one that could break from an auto-update because the maintainers decided to make some massive change without consideration for the users.
    - prophesi 4y ago
IncRnd 4y ago
They are not the exact same experience. VSCodium does not offer remote development over ssh. There are other addons that only come with VSCode, but the ssh difference was the main one for me, not the extensions.

by jxf 4y ago

Cupprum 4y ago

Some Microsoft extensions do not work in vscodium. I have been using it for more than a year now, but i still miss the remote development using SSH.

fartcannon 4y ago
You get all that for free with a terminal in Linux. And KDE has all kinds of tools that remotely work with SSH. Dolphin can, for example, treats a remote SSH connection like a local file system.
- hughw 4y ago
  How does a Linux terminal replicate the remote capability of VS Code?
  - pxc 4y ago
    What does the SSH capability let you do, exactly? Just edit remote files as if they were local?
    - jaywalk 4y ago
      It basically runs everything on the remote machine. So when you hit F5 to debug, the code is actually (transparently) running on the remote machine. It's pretty cool.
      - fartcannon 4y ago
        Since KDE 3.5 (2002) you can use SSH to mount folders in the file manager and modify not just code remotely as if it was local, but other files too.
        jaywalk 4y ago
        Not even close to what this does. It basically runs a headless version of VSCode on the remote machine, with all of the necessary extensions, and your local version of VSCode controls it.
        fartcannon 4y ago
        When you SSH into something, you type, for example, 'vim' into the terminal, and then you're running the remote version of vim on that machine. If however, you want to use your local version of vim, you can do that too. With the previously mentioned kde tools. Is it something different than that?
        jamesgeck0 4y ago
        Yes, this is different. Vim is a TUI application which can easily run over vanilla SSH. VSCode is a GUI, which cannot. VSCode Remote runs the editor in a client/server mode, with all the UI running on the client and everything else seamlessly running on the server. There's none of the typical latency you get by running heavy operations such as full-text search on a mounted remote filesystem because they're run on the server.
        fartcannon 4y ago
        So, ssh -X? To me it sounds like a lot of needless bloat but cool, glad to learn a new thing.
        lights0123 4y ago
        That will run both the backend and the frontend on the remote server, while VS Code SSH will only run the backend on the remote. ssh -X is very slow for a complex GUI across a non-local network.
runeks 4y ago
> […] but i still miss the remote development using SSH Me too. Editing text is pretty light weight, so it makes sense to run locally. But the language server is often rather heavy weight, e.g. requires compiling all project dependencies, so it makes perfect sense to run this on a beefy remote machine (connected to wall power).
jxf 4y ago
Which Microsoft extension specifically is that? There are quite a few MS ones that have Codium equivalents which are effectively identical, though I don't use the one you're referring to.

kimbernator 4y ago

I used vscodium for a while up until this change was made. The maintainers changes the extension registry to the new one while it had something like 40 total extensions available without any sort of meaningful notification to users, and in a minor version release no less. Pretty shitty move, IMO. I have trouble trusting maintainers that are willing to push such drastic changes without letting people know.

prophesi 4y ago
By April 2020, it had roughly 200 extensions because there was no push for marketing it just yet. By the time VSCodium implemented it in June 2022, the push to move extensions over was in the works, and hundreds more were added. Also have been using VSCodium for years and the transition had no effect on my daily work, despite needing plugins on new machines for the relatively niche language of Elixir.
- kimbernator 4y ago
  I'm sure it works fine now, and I don't doubt that it was fine in your case, but it was a huge inconvenience for me and the maintainers were pretty unhelpful about it when people complained. It literally took 9 months for a feature to be added that allowed changing the marketplace a user wanted without it being overwritten by updates. https://github.com/VSCodium/vscodium/issues/418 https://github.com/VSCodium/vscodium/issues/418 The correct way to do this would have been to start with a way to persistently change the marketplace URL being used and having the change be opt-in, then having a major version release when the default value was changed, including obvious instructions about how to change the desired marketplace. Instead, people were told to do the work themselves of porting over the extensions they wanted. That's a great way to get people who don't have the time or interest in that to just abandon the project altogether. Even if it is fine now, I just don't want a tool I use for my daily work to be one that could break from an auto-update because the maintainers decided to make some massive change without consideration for the users.
  - prophesi 4y ago

IncRnd 4y ago

They are not the exact same experience. VSCodium does not offer remote development over ssh. There are other addons that only come with VSCode, but the ssh difference was the main one for me, not the extensions.