I'm a little confused. Are these translations not in source control? Can you not revert the changes since it was introduced?

Sure sounds like an LLM.

It's not exactly like vim, and there are plenty of vim plugins that don't work with it (anything vim8 onward). There has never been a 1-to-1 correspondence, the gulf widens as both develop different features with different philosophies.

The most egregious offense on Neovim's part that I can't get past is the removal of access to the shell in which you run vim (via :!, :w !, etc.). Vim is so much more capable of being closely intertwined with the shell, whereas neovim requires everything to be done through terminal buffers (speaking of which, vim's terminal buffers are a lot better than Neovim's).

Also, Lua is really overrated and worse for vim scripting than vim9script (which is both more native to vim and faster).

Most of vim is not emulated. It's very surface-level and limited. The closest is evil mode for emacs, which is decent, but still lacks a fair bit. The emulators in Intellij and VsCode are paltry in comparison to what vim can do.

She has always been pretty shit. That much is indisputable.

Voting for her was still the correct thing to do (and what I did), because the degree of Trump's fascism and corruption is much greater and more dangerous.

But it's incredibly naive to think this behavior of hers is in any way new. It's exactly who she's always been.

My company did the same, yet they approve of tools that have shown countless security breaches (such as Microsoft Copilot).

It's a complete joke.

The OP is on feddit.uk, so most likely not an American.

The question is also just that, a question. Not an expectation.

That's why vim is so great: it has a ton of power built right into it without customizations, and it's already installed on basically any unix-like system. Unlike, say, vscode, it can do a ton of stuff out of the box without any plugins at all.

dot is the file for.at used by graphviz, and tbh it seems pretty close to what you're describing. There's a number of tools that can consume (and produce) the file format.

It's the format I've worked with on occasion (though admittedly it was because it was what was produced by other tools).

It's not as big of a deal as you might think. You still have a lot of your muscle memory from regular keyboards. It might take a little while to adjust when switching between the two, but it's not that bad.

If you switch between the two enough, you can actually type on both equally well.

A lot of mechanical keyboards these days are programmable using QMK Firmware. I actually use https://www.caniusevia.com/ instead though, which uses (a subset of) QMK under the hood but allows programming the keyboard via a Web app on the fly.

For my layout, I have the standard QWERTY layout for the unmodified layer (layer 0, holding no keys). Then I can hold down a thumb key for switching to a different layer, which has things like symbols, F1-F12, Home, End, etc. The layout I use isn't too far off the default Iris layout, just a few tweaks here and there (like one that allows me to hold a key for control, or tap that key for escape).