You don't need multi-cursor selection in vim.

Vim has all the tools necessary to achieve the same end result with the same convenience. [0]

Just thinking about what crazy things I've done with macros that multi-cursor would be incapable of handling makes me chuckle.

vim doesn't need the fancy features of other editors (except for maybe LSP and tree-sitter for a more IDE-like experience).

The core problem is that you don't grok vi [1] which is fine, not everyone has time and passion for that. But please don't think for a moment that vim is inferior just because it doesn't blindly copy other editors features.

[0] https://engagor.github.io/blog/2018/02/21/why-vim-doesnt-nee... [1] https://stackoverflow.com/a/1220118

Judging by https://github.com/mawww/golf kakoune is capable of completing the majority of the same editing tasks as vim in a very similar amount of keystrokes. The main advantage of multiple selections is that you can see which text you will operate on ahead of time, rather than having to first select which operation you want (delete/yank/change/etc) and then which text it will affect. I think pointing out that vim's selections aren't as capable as kakoune's is a fair response, and saying that you can accomplish similar things without selections is a bit of a deflection.

80 Better 18 Same 35 Worse

Golfing is not the best representation of day to day text editing, but I must say that optimal Kakoune solutions are usually pretty close to normal workflow.

> vim doesn't need the fancy features of other editors (except for maybe LSP and tree-sitter for a more IDE-like experience).

Both of which neovim has.

Agree with your premise, though: (n)vim does not need multi-cursor selection, for the reasons have given.

Don't get me wrong, I'm a nvim + LSP + treesitter user. :)