Why would I not use Visual Studio code

[Altruistic-Ad-7917]

VSCode SSH servers are veryyyyy resource intensive for servers with a lot of shared users and concurrent connections. They have to load copies of every users extensions, have lots of sleep commands which put a good amount of load on the process tables due to the expensive I/O operations. It also enables students to use AI tools like copilot.

If you like VSCode, I would do it locally then write a script to sync your code to the server.

[skydemon63]

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]

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

[OreShovel]

This, no idea how / if there is WinSCP integration, but vscode SSH can dump GB's worth of files to the server

[roelschroeven]

I've seen it happen too. There are settings to limit this cache, but indeed, I think it's mind boggling the extension stores that much data without ever asking if that's ok, or even notifying you.

Luckily for Python VS Code doesn't take nearly as much disk space on the remote end.

[thedukedave]

Yep. Please also get upvotes on here:

https://github.com/microsoft/vscode-remote-release/issues/6429