vim does not break vi concepts the way neovim breaks both vi and vim concepts.
It's not 'vi with lua support' it's a totally different core paradigm like the difference between vscode and vim.
Someone recently wrote a whole screed about this and itemized a bunch of points about why exactly it's backwards to integrate a terminal vs working within any terminal, baking in more limited answers for things that are already answered more flexibly by plugins and external processes, etc. They got a little bit screedy and there were a few nits to pick, but the basic points were all both true anc valid.
It was posted to HN within the last couple days but I can't find it now. If I find it I'll add the link here.
All of which is not to say that neovim is necessarily a bad thing, it's just that it's not a newer or better vim, and the starting point being a fork of vim doesn't mean a thing.
The first Tesla was a fork of a Lotus.
Both Tesla and Lotus are fine cars, but a Tesla is not a newer better Lotus.
If you like the design goals of Lotus, then a Tesla is utter garbage.
And the inverse is exactly the same true. If you like the design goals of a Tesla then a Lotus is utter garbage.
If I were either Lotus or a Lotus user, and even if cars were open source projects without legally enforcable trademarks on their names, I would be highly highly annoyed when someone comes along and takes the current Lotus and replaces the engine and transmission with electric motors and a PC, and slaps a huge ipad on the dash, and then names it "NeoLotus", and then continues to call it NeoLotus even after the original Lotus base isn't even in there any more and it's a totally different thing with a totally different set of priorities, goals, philosophies, and audience.
