> I don't really understand the culture of all the > customisation/plugins/etc. around text editors 1) small, basic install of (neo)vim for most users 2) tota

> I don't really understand the culture of all the > customisation/plugins/etc. around text editors 1) small, basic install of (neo)vim for most users 2) totally separate extensions for those who need them without making the core app harder to test > it's small and simple Allowing plugins doesn't make the app any more difficult to use. And, of course, one thing some plugins do is make stuff easier than stock vim. IE rather than going: :e ../../src/java/blah.java you could use one of the many fuzzy searc plugins and do something like: <C-p> sjablja (ie just typing some of the letters from any part of the path and file name as long as it's in the correct order). > I don't expect or need much from a text editor in the > first place It's primarily a programmers editor, replacing for many people any IDE at all, so it's nice to be able to select a word and press a key and have that file open; jump between viewports on multiple files on multiple tabs; have word completion. None of what I've described is some rare edge case. One thing I use vim for is to get the results of grepping thousands of source code files, then trimming down the results using "remove lines matching this", "remove lines not matching this", or turning lists of filenames into dos or bash commands. Sure, you can do all this with bash but I don't know all the commands anything like as well as I know how to do this sort of stuff with recordings or regex within vim.