3 ms·

I use development virtual machines to segment projects and clients also although I just run my editor in each VM. What's the benefit of the vscode remote hosts/

I use development virtual machines to segment projects and clients also although I just run my editor in each VM. What's the benefit of the vscode remote hosts/dev containers over a normal remote session?

campbel 3y ago
In my experience its mostly the input lag when dealing with the remote environment. I'm quite sensitive to delays in editor input, so I prefer something native. If you aren't sensitive or your remote connection is fast enough for your preferences, I don't think there are many other advantages.
satvikpendem 3y ago
GPU acceleration is not always guaranteed on the VMs, as well as input lag.
noodlesUK 3y ago
I find that the experience doing this is essentially unbearable due to graphics problems on retina displays, input lag and the like. I also figure that the kind of person who wants an editor which is designed to paint as fast as possible probably wouldn’t want to have a whole VM and spice/similar client sitting between them and the editor.
xnyan 3y ago
> I just run my editor in each VM In addition to lag and a poor visual experience as others have mentioned, there's the issue of two (or more) operating systems with two separate shells/UIs. When using VMs or a VDI/remote desktop the cognitive overhead of remembering which OS shell I'm in for the purposes of keyboard shortcuts, clipboard, switching between programs and etc impacts my productivity significantly. VSCode (or any other editor with similar features) shell is great because it completely separates the editor environment from the dev environment. I can run as many instances of VSCode as I want each with their isolated dev environment of the target host, but all managed by one shell, one window manager and one clipboard.
mixmastamyk 3y ago
sshfs solves most of these problems and I’ve found it good enough. Better than switching to a partly proprietary editor anyway.

campbel 3y ago

In my experience its mostly the input lag when dealing with the remote environment. I'm quite sensitive to delays in editor input, so I prefer something native. If you aren't sensitive or your remote connection is fast enough for your preferences, I don't think there are many other advantages.

satvikpendem 3y ago

GPU acceleration is not always guaranteed on the VMs, as well as input lag.

noodlesUK 3y ago

I find that the experience doing this is essentially unbearable due to graphics problems on retina displays, input lag and the like. I also figure that the kind of person who wants an editor which is designed to paint as fast as possible probably wouldn’t want to have a whole VM and spice/similar client sitting between them and the editor.

xnyan 3y ago

> I just run my editor in each VM In addition to lag and a poor visual experience as others have mentioned, there's the issue of two (or more) operating systems with two separate shells/UIs. When using VMs or a VDI/remote desktop the cognitive overhead of remembering which OS shell I'm in for the purposes of keyboard shortcuts, clipboard, switching between programs and etc impacts my productivity significantly. VSCode (or any other editor with similar features) shell is great because it completely separates the editor environment from the dev environment. I can run as many instances of VSCode as I want each with their isolated dev environment of the target host, but all managed by one shell, one window manager and one clipboard.

mixmastamyk 3y ago

sshfs solves most of these problems and I’ve found it good enough. Better than switching to a partly proprietary editor anyway.