News for hackers. Stuff that matters.
Re:Neovim v0.4.0 by alpaca128 on Monday September 16, 2019 @06:54AM (#20982807)
Because Vim modes usually don't support more than a handful of basic features, let alone plugins and custom keybindings.

Vim also starts up without any noticable delay and can be used for every text file, no matter in what context.

Re:Neovim v0.4.0 by m712 on Monday September 16, 2019 @08:09AM (#20983241)
>Vim also starts up without any noticable delay

Only if you run it without any plugins. Unfortunately if you have a lot of third party packages, vim startup times start to get closer to emacs startup times (both of which are still better than any IDE I have used, of course). I keep a vim.norc alias in my alias file which launches vim with an empty .vimrc for this very reason.

Re:Neovim v0.4.0 by alpaca128 on Tuesday September 17, 2019 @02:19AM (#20992188)
Strange. I use 15 plugins and according to the --startuptime flag NeoVim takes 32ms to start. Vim takes about twice as long, but that's still so incredibly fast I'd call it instant. I guess when it comes to plugins there are some real heavy-hitters out there that I somehow managed to never try.
Re:Neovim v0.4.0 by wruza on Monday September 16, 2019 @12:47PM (#20985957)
You could use autocmd for filetypes that require plugins, so they don’t load for configs/texts. If your pm of choice allows this separation, ofc.

I’m not very experienced with complex plugins, but most of what I’ve seen did nothing unless explicitly initiated. Maybe there are global variables to control that.

Re:Neovim v0.4.0 by soraminazuki on Monday September 16, 2019 @08:07PM (#20989820)
I've found that profiling startup time and lazy loading plugins could reduce your startup time to 100~200ms even if you have more than 50 plugins.