Except for the remote extensions, Pylance, and Live Share, IIRC. Which are pretty important to a lot of people's use of VSCode.

The one extension I use the most is the remote access via ssh, and that's not available on vscodium last time I checked. Only reason I'm still on VSCode.

You can download the extension as a file from the vscode marketplace and install it in Codium. The remote containers extension requires the latest Codium but it work now.

Thanks!

ok it installed but more might be needed to make it work..

haven't tried this yet: https://github.com/VSCodium/vscodium/blob/master/DOCS.md#pro...

sshfs? Then the solve is outside the editor.

That's my workaround, but it's less convenient.

I don't find it to be a workaround. The remote development stuff loads a bunch of projects and processes onto the remote host. I have some pretty small VMs that I run some older production servers in. Which is my principal use case for remote development.

Connecting to them this way brings them to their knees. That and seeing a host of new high memory processes doesn't give me warm fuzzies about the security risks on important remote systems.

Pretty much why I'm using sshfs and not the VSCode remote.

And Atom over sshfs, and crawling the whole project before showing a window is a deal breaker for me

While it can run the same extensions, some have to be requested to be added to the code-oss repository, as there are some things that I noticed aren't there, and the path recommended to those in this situation is to ask for them to be added on an as-desired basis.