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.