So a program that is specifically designed to edit files and run arbitrary commands on a remote machine... can do so. Not sure where the bananas part comes in. Sending a binary over SSH/SFTP might sound weird at first glance, but VSCode can't assume that your remote machine can access the wider internet, and it needs a reliable way to bootstrap the agent on the remote. Shipping it over the SSH tunnel is the natural solution.
I think the actual concern, not well expressed in the blog post, is the fact that node and vscode server are installed on, for instance, a prod machine that (probably) should be very tightly controlled in terms of what software is installed and running. You don't want to unwittingly add to the attack surface
The very first page[1] of the VSCode remote documentation makes it perfectly clear that VSCode remoting is more akin to running an Emacs server on the remote than TRAMP.
10000truths · · focus · HN ↗
bobtheborg · · focus · HN ↗
pstuart · · focus · HN ↗
K0IN · · focus · HN ↗
also "i just want to edit a config file and i want a nice ui", is how you get there.
doc_ick · · focus · HN ↗
jasomill · · focus · HN ↗
[1] <a href="https://code.visualstudio.com/docs/remote/remote-overview" rel="nofollow">https://code.visualstudio.com/docs/remote/remote-overview
brabel · · focus · HN ↗
jayd16 · · focus · HN ↗