[Barrin92]

>There are a ton of people that use Vim because it's productive, not because of how "lightweight" it is. I see no reason to shame people if they choose to use "heavy" plugins to achieve whatever functionality they want.

because vim wasn't exactly built with these kinds of features in mind and it shows when you start to throw a lot of IDE features into vim. For example switching to very large text files with vanilla vim, doing some search and replace is no problem, it's super fast.

Doing that with the wrong plugin on that does some CPU heavy stuff can very quickly make vim unresponsive.

IDEs are already built with a rich feature set in mind, so you can expect performance to be relatively stable. Vim or Emacs with the entire kitchen sink thrown in tends to be a little bit dicy

[nobleach]

Perhaps. But since it's not main-lined into the actual application, it's no big deal. If people want to "pimp" their Vim with airline, and any other odd nonsense, that's fine. If they want to include an entire nodejs process to provide auto-complete, that's fine too. I'm simply saying that the fact that it was originally conceived as a lightweight text editor, doesn't mean that people should be shamed for making it so much more. I personally have found Vim to be my favorite tool, and nearly EVERY attempt at other IDEs to emulate it, I've found lacking. So, I choose to extend Vim.

[soraminazuki]

> because vim wasn't exactly built with these kinds of features in mind and it shows when you start to throw a lot of IDE features into vim.

I disagree. Both Vim and Neovim are under active development, and have acquired many features to support IDE functionality.

> For example switching to very large text files with vanilla vim, doing some search and replace is no problem, it's super fast.

This has improved a lot in the last few years thanks to the async APIs.