logoalt Hacker News

tikotusyesterday at 3:26 PM4 repliesview on HN

I'm glad to hear the SSH remote editing is working well.

A lot of the time I'm developing on a remote server using VSCode Remote-SSH. I mostly love it. But! It consumes a lot of memory. And not only that. At times it gets stuck in some infinite loop or such, and ends up consuming all memory on the machine, preventing all traffic. Takes a few minutes for the OS to finally kill it, so I can get back in. I'm pretty this is happening due to large collections of symlinks (the subprocess eating up the memory is rg). But also just JavaScript editing at times launches up a bunch of ts-servers consuming everything and more.

This is super scary, if I'm poking around on the prod server.

Looking for alternatives. Zed is on my list.


Replies

apitmanyesterday at 7:07 PM

The VSCode remote ssh implementation is a bit concerning:

https://fly.io/blog/vscode-ssh-wtf/

Any idea if zed does things differently?

Pyrodoggyesterday at 4:00 PM

Do you happen to use the AutoImport extension? rg subprocess explosion seems related.

https://github.com/soates/Auto-Import/issues/127

eknkcyesterday at 6:45 PM

I've been using the SSH remote editing on Zed too and it works great. No issues whatsoever.

whalesaladyesterday at 8:28 PM

The only reason I remained on vscode for so long was the remote ssh editing as I also use a dev box (M2 air + dev box = multi-day battery life) but recently got sick and tired of the vscode instability and frequent need to blow away state / reinstall plugins after updates. When I saw Zed had an ssh dev equivalent I jumped ship and haven't looked back. Here is my theme if anyone is interested, https://github.com/whalesalad/dotfiles/blob/master/zed/whale...