For remote development there is Fleet from JetBrains which is still in preview but mostly works (year ago it had a lot of issues). Nonetheless, it still needs a lot of improvements (rendering performance IME is poor, some functionality is missing in comparison to full-fledged IDEs like IntelliJ)
There is also JetBrains Gateway which allows you to run IntelliJ/PyCharm/etc. remotely. I'm using it and it is very usable, however, there are occasional bugs which could be explained by synchronization issues
Btw. Vim should be very usable over ssh (especially with tmux and maybe iTerm2/other terminal integration with tmux' control mode - tmux panes are native windows, new terminal window/tab creates new tmux window/pane etc.). Why are you using VSCode over Vim for remote development?
I kinda lost hope for fleet when it just started loading the intellij core to do all relevant stuff. I wanted that new editor so it would be faster, not so that I can have slightly different chrome.
Re:Leaving Neovim for Zed
by FireBeyond on Sunday August 18, 2024 @09:42PM
(#41287086)
> Why are you using VSCode over Vim for remote development?
Who's to say you have shell access to the remote instance?
Vim has netrw. No need for a remote shell
Why don’t you have shell access? That is the minimum for doing any kind of development. And I think the vscode plugin relies on shell access to install itself (either ssh or whatever protocol for docker)
HOWEVER..
It has a killer feature if you are doing remote development.
It (mostly seamlessly) presents the remote (ssh, docker, wsl) as if it was local, and I've yet to see another editor do it as well and as cleanly.
So much so that when doing remote development I'm prepared to put aside VSCode's other shortcomings for the superior remote development experience.
For local development I still use vim+terminal, but if I'm in a situation where development needs to be done on a remote machine, the VSCode vim bindings are good enough that I'll probably be using VSCode.