Including almost all extensions, which install into the remote.
Whereas with VSC Remote, all of that stuff works exactly as if it was local. After 30 years of using unix I'm fine with that if I have to do it.īut you lose all the editor integrations, because git cannot work effectively over networked filesystems. Yes, you obviously could/can do all of your git stuff in a terminal window - that is how I used to work even with VSC before the Remote facility was added. Plus you can edit very large files remotely. This is the underpinning of a pair-programming aspect of remote VSC that MS intend to productise.Īnd if you log into that machine and edit a file that is open in VSC Remote using something like vi, VSC will know about the changes. In fact, if you log in twice to the same remote host as the same user using VSC, your editors will magically update each other, live. So there is no risk of block corruption (which has bitten me on the arse before). Sometimes a nice butcher's knife is more useful than a Swiss Army tool.īasically it's not running a block filesystem over SSH at all.
Nova (like Coda before it) is definitely more of an editor with some IDE-like enhancements than a full IDE, and I'm fine with that (in some ways Nova is even more focused since Coda had a built-in documentation reader and MySQL client and other tools I never used). Well, for search, there's still grep/git grep/ag (the built-in multi-file search might actually work over SSH never tried it since I don't use it locally either), and for git, there's still, well, git. The Remote mode operates a full remote VSC environment over SSH or as a docker container, and that means things like being able to do find and replace at the remote end in the editor, but also manage git at the remote end using the built-in source control etc., but also it means support for extensions and build tools that run remotely. > And this really doesn't get close to what Visual Studio Code's Remote editing functionality can do. I'm sure it does fine at that, but there are perils with SSHFS-type access (like file corruption risks when you switch between editing machines.)
0 kommentar(er)
