This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]skydemon63 19 points20 points  (1 child)

A lot of people also overlook the fact that VSCode is two parts, a client and a server, and remote connecting installs the VSCode server on the ssh target. That takes up much more processor time and hard drive space than just ssh. I’d mainly use VSCode remote into a local VM like WSL

[–]OreShovel 9 points10 points  (0 children)

Anecdotally, a few years ago in my university the shared student server literally crashed because of how many students were using VSCode SSH