> You can effectively run whole development (LSP, docker, compiler, files) on remote like it is on your local machine.
the same is possible with any other editor that implements a client/server model, and it can be done without giving the server the ability to execute code on the client
> If any of you are recommending sshfs or a like you really don't understand the benefits of full VS Code SSH Remote environment.
Or we don't need them. Most peoples workflow is send file to remote, trigger remote. There are definitely other cases that this plugin may be more suitable for, but the trade offs for most people (which I suspect the majority of developers don't understand) are not very good.
You can effectively run whole development (LSP, docker, compiler, files) on remote like it is on your local machine.
You can turn any underpowered legacy machine or a thin client to a full featured workstation.
There is tons of horrible plugins that scream security threat in VS Code market place. The SSH Remote or VS Tunnel ain't one of them.