Unless you need a graphical debugger, then vi/vim/nvim/emacs all start to get creaky. That single requirement keeps me on vscode. I'd love a terminal based alternative.

Graphical as in integrated with the normal editing view? There's a new very nicely done one for Emacs: https://github.com/svaante/dape . The documentation about using it is currently a bit terse though.

I actually don't mind if it's not integrated with the editor. I'm fine with a debugger being a standalone application. What I want is the ability to see the source, set breakpoints and navigate the code efficiently inside the debugger. vscode is currently the best option for this remotely

just don't write buggy code ;) (or have to work on anyone else's)

> The learning curve is steep

So it's not "a little bit of work"

Compared to mastering C++, vim is a piece of cake. For me it was a major productivity boost.

Try remote development with vim over 200ms ping ssh connection

I've tried that, but in this case i would just NFS/sshfs share the directory and work with vim locally.

Vim can also read and write files across networks (while running locally): vim scp://user@myserver[:port]//path/to/file.txt should work.

If you want to run builds and such on a terminal, just have a tmux window with an active ssh connection.

There's a solution to most issues out there.

>Try remote development with vim over 200ms ping ssh connection

Isn't such a scenario (high latency dialup) what vi was originally designed for?

I have frequently done full vim editing on primary development boxes across cross-Atlantic pipes, which are usually 150ms from where I am in the states. Not really a bad experience in any way, tbh. I'm sure my tolerance level would decrease dramatically at 300ms though.