Hacker News Reader

Comment by j2kun | Hacker News Reader

I am very opinionated, but I really don't like Cider V. I have been using neovim at Google since 2017 and it's been great.

View on HN

This is the way.

But the downside is that you do get the Cider team constantly messaging and asking for reasons you won't switch. I gave feedback that their Vim bindings were broken (it would sometimes fail on holding down directional hjkl for no reason) but I'm not sure if they've fixed it since I left in 2023.

Cider is good for writing g3docs though.

I can't say for sure because I never used it, but neovim is the jam.

same! how do you deal with cloudtop latency though? sometimes my neovim is very slow and laggy because of the remote connection / network file system

I use a workstation specifically to improve latency. Needed to get approval at some point to get a refresh though.

like a workstation under your desk? is the latency bad when you remote access it not in the office?

Yeah, under my desk. I rarely remote which is a good excuse for me to disconnect from work anyways.

Ever tried SSH'ing via "Mosh"? https://mosh.org

I have a (Google-issued) desktop in the same city I live in, so the latency is not so bad.

I will say that the latency of the filesystem is a different problem. Most of the google filesystem tooling is not built for command line tools that expect to index large subsets of the filesystem at once.

Spin up one in the US central region instead of an instance near your satellite office. The bottleneck is usually not your shell connection to the instance but the connections from the instance to all the infrastructure that's mainly based in the US.

Cloudtop to run builds, g4 commands, etc., and srcfs / srcfsn to actually write code. (caveat: I have never used neovim, so I don't know if that is different).

Mosh instead of ssh. Works well enough for as long as it works.

Road warrior even supports it.

But i keep going back to regular ssh or shpool with roadwarrior.

Reply on news.ycombinator.com