Yes. I tried Neovim last year. Spent 1 day, and did not achieve parity with my Vim setup so I abandoned it. A contributing factor may have been: getting distracted with analogous plugins on the nvim side. Now that Bram is gone, I'll take another day or two and switch over sometime this year. I don't have to though. Vim works. It always has. It probably always will.

Vim has been a great companion in my life, thanks Bram. People wonder why this 30 year old piece of software is so beloved. Most will never know.

I enjoy typing 'vim' to start it up. I've created aliases for other programs, but not vim. 'v' would work quite well in my setup. I love those 3 letters.

It seems that you're implying that nodes cannot be synchronized within the time it takes for light to travel between the nodes.

Images both nodes having their own atomic clocks. Now allow them to timestamp transmitted and received messages with very high precision.

In a white-rabbit network you don't need atomic clocks on each node. One atomic clock is enough, its frequency is distributed over the network.

15 seconds per month is about 6.7ppm. That's well within typical crystal oscillator accuracy. If you need more than that (without external time correction such as gps or radio/internet), you need expensive oscillators with temperature compensation or even ovenized units.

This is my exact use case. I disabled federation, hand out account tokens to my kids' friends so they can make their own accounts (public registration is disabled). I used that popular Synapse Ansible deploy project, and deployed it on the cheapest Hetzner VPS. Been running flawlessly for over a year now.

Because mobile (basically ARM) is not a standardized platform like the PC. PC architecture has dozens of interoperability standards the entire PC ecosystem adheres to. Everything from boot up, to DMA controllers, to protocols for device capability discovery, and more .. You can think of each ARM board as its own bespoke platform (needing it's own device tree/bsp).

If you're already comfortable with an editor (such as VSCode), don't worry about learning another one unless you inherently enjoy the journey (which it seems that you don't). Instead, invest some time learning features, keyboard shortcuts, and configurations of your current editor.

Also, if you use languages for which an IDE provides significant value - continue using whatever IDE you are using (... if you don't enjoy the vim/shell lifestyle). Vim is not an IDE, though it can eventually be configured to act like one. If you mainly program in C for example, an IDE provides minimal value beyond what a lightly configured Vim would provide.

Source: Near-full time vimmer and terminal tools user. I found joy in the journey as an end in and of itself.

Extract windows product key just in case. Install Kubuntu. Pull dotfiles from GitHub, and run installenv.sh . Done, I'm home.

1. Fugitive.vim 2. Fzf.vim . If you launch vim from a path includes both repos, it will just work. If not, you can provide a starting path argument to the fzf file picker. 3. ctags (universal-ctags) + native vim tag jump functionality. Pair with gutentags plug-in to auto generate ctags when files change and the such.

You can also use "git difftool <commit>...<commit>" (with 3 dots).

https://git-scm.com/docs/git-diff#Documentation/git-diff.txt...