That's useful, but I think the person you were replying to doesn't just use the host machine as a remote file system but also as a build host and to have a single workspace with all its settings available from any machine.
I recently set this up as well using code-server [1], which works brilliantly. I have a VM running on a powerful hypervisor host, which has all the source code, the workspace configuration with all my customisations, build tasks, etc. Compilation is fully on the host side, which is a 12-core with 32GB memory, way beyond any of the computers I use as clients, and all I need to access it is an SSH connection to it. Code-server has a progressive web app mode that makes it pretty much indistinguishable from running a local installation. First time I have had to acknowledge it wasn't such a bad idea to implement VSCode as an Electron app to be honest.
Re:Insider Build of VSCode for Windows/ARM64
by AaronFriel on Friday May 29, 2020 @01:56PM
(#23353259)
The ssh extension actually does all of that as well, but it does mean the frontend runs in the Electron app vs in a browser. The first thing the ssh extension does is install the VS Code server backend in the remote host, enabling the remote host to run extensions, the terminal, and so on.
https://code.visualstudio.com/docs/remote/ssh