zlacker

Hey! I'm a Sublime Text user since ST2 in 2011.

I love ST (my last blog post is https://blog.separateconcerns.com/2025-01-04-teal-lsp-sublim...) and I think the main thing lacking compared to the competition is the remote development experience.

I work in AI so we typically work over SSH on machines with big GPUs. Most of my colleagues use VSCode because it has a very good Remote Development extension.

>>catwel+(OP)
Can't this be solved using a remote file system these days?

I haven't done it in years since with every customer from the last few years the only official way to get to prod is a CI-pipeline, but I think I remember using sfpt or ssh-based file systems even a decade back?

>>eitlan+c2
You can use a remote FS but it is nowhere close to the experience VSCode gives you. For instance, running code will run it locally, not on the remote machine.

>>catwel+(OP)
Likewise!

The only reason I moved away from subl is that I got access to a big ass machine and I needed to work remotely. The performance of VS code here is so good that often times I forget that the code and terminal is not my local machine.

>>catwel+(OP)
This! Upvote for ST SSH remote development, currently using ST for local dev and VSCode for remote.

>>catwel+(OP)
Same here, for 15 years. I mainly use vi on the remote machine.

>>catwel+(OP)
My preference is that it could use .ssh/config to explore the remote machine and then open/edit the file/dir.

>>catwel+(OP)
I actually have heard that working over a remote connection can be a pain. From what I've seen from other Sublime users is that they will usually just mount a drive and then edit off that. There are also a couple of SSH plugins that can be used. In the past, I've just downloaded the files I've needed and then used rsync or scp. Not slick, but it works.

>>catwel+(OP)
Remote development is VSCode's killer feature.

>>catwel+(OP)
This would be my top feature request. In addition to being great to have generally, there are increasingly environments where this is essentially a requirement and local copies are often verboten so you can't just use rsync/ssh.

>>catwel+(OP)
Same experience. My local machine at $Job is so slow and locked down that spinning up a VM in the cloud + VSCode remote plugin is the only way I can develop now. I would not have switched if I could edit the remote filesystem without syncing. I've worked on a ton of projects with the paid SFTP plugin but it was too painful in this case.

>>achair+wd
IMO remote mounts is a feature of the OS.

For Linux and macOS, you can mount ssh directly.

Unfortunatley, Windows makes it a little more complicated.

But there's hope. You can use yasfw with dokany (dokan fork).

https://github.com/DDoSolitary/yasfw

https://github.com/dokan-dev/dokany

Or mount from inside WSL.

>>zxvkhk+dE2
In principle I agree, in practice I haven't found an OS based filesystem mount that works as reliably as vscode. In particular, I mean the connection is relatively robust, reconnects automatically most of the time after an outage and editing is totally asynchronous, i.e. there's no noticeable pause after saving before continuing editing and no lag (other than what's induced by the electron) when editing.