4 ms·
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.
by 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 agoYou 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 agoHow does a Linux terminal replicate the remote capability of VS Code?
- pxc 4y agoWhat does the SSH capability let you do, exactly? Just edit remote files as if they were local?
- jaywalk 4y agoIt 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 agoSince 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 agoNot 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 agoWhen 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 agoYes, 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 agoSo, ssh -X? To me it sounds like a lot of needless bloat but cool, glad to learn a new thing.
- lights0123 4y agoThat 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.
- fartcannon 4y agoFirst off, VSCode is a text editor, not a complex GUI (or at least it shouldn't be but hey who knows). Second, the point is that you have been able to achieve funcrionality through means available using only a terminal, and vim/ed/nano wince forever. And additionally, do quite a bit more with things like the FISH sessions in KDE as early as 2002, probably much earlier still with other tech.
- pxc 4y agoYeah that does sound like TRAMP. I'm sure it's pretty nice.
- 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 agoWhich 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.