3 ms·
I wondered a similar thing regarding remote development using VS Code's remote-dev plugins (for SSH and/or Containers). I've done this workflow (i.e. used a lo
by mattlondon 6y ago
I wondered a similar thing regarding remote development using VS Code's remote-dev plugins (for SSH and/or Containers).
I've done this workflow (i.e. used a local VS Code to develop on code hosted on a remote machine) quite a lot, but always using fairly well specced laptops (Core i7s, 16+gb ram etc) to connect to the remote and the experience has largely been seamless.
Anyone got any experience of this?
Looking at my local VS Code now as I am connected to a remote SSH host working on a very small python workspace it is using a couple of hundred meg of ram and fluctuating from 0-2% CPU on a i7 quad core. I don't have a large workspace in something more demanding (i.e. something where the IDE can do something useful unlike with python where it is a glorified notepad) to test with right now though :(
- Macha 6y agoA Surface Go has been computationally sufficient for remote SSH dev use for VS Code with Rust with my (admittedly small) projects. I no longer bring my XPS 15 when visiting parents for extended visits. The 10" screen/keyboard is a drawback, obviously, but performance hasn't been since it's the remote machine doing the heavy lifting.
- Macha 6y agoSince the edit timer has expired, I will point out that it's the 8GB/SSD model I have experience with. Total RAM usage is over 4GB and I'd expect the eMMC model to be just generally a bad time.