I have some doubts about the long-term future of https://mutagen.io/, but otherwise I have found it’s really good; real time sync over ssh. I have a few niggles about it, but it really unlocks a ton of possibilities.
The biggest disadvantage of VSCode remote is that it needs to install a server on the target machine. If you’re remoting to a slightly weird OS (non-glibc based or some ARM platforms), the solution described in the article may be a better experience.
I used to do something similar using a headless VM running locally. I also configured my editor projects to do rsync+build when pressing Cmd-B. The best part was build errors appearing natively in the gutter and underlining relevant text in addition to the build output panel since the editor knew how to parse compiler output.
EDIT: here’s a faster way to run the rsync, --update being the most relevant.
I have some doubts about the long-term future of https://mutagen.io/, but otherwise I have found it’s really good; real time sync over ssh. I have a few niggles about it, but it really unlocks a ton of possibilities.
I just use Visual Studio Code with the Remote - SSH extension… Seems simpler, but I guess if you hate VS this is an option…
The biggest disadvantage of VSCode remote is that it needs to install a server on the target machine. If you’re remoting to a slightly weird OS (non-glibc based or some ARM platforms), the solution described in the article may be a better experience.
Great point.
I used to do something similar using a headless VM running locally. I also configured my editor projects to do rsync+build when pressing Cmd-B. The best part was build errors appearing natively in the gutter and underlining relevant text in addition to the build output panel since the editor knew how to parse compiler output.
EDIT: here’s a faster way to run the rsync,
--updatebeing the most relevant.