Post

For the longest time I was curious to measure the exact impact of how number of loaded #neovim plugins affects performance. So I finally did it: echasnovski.com/blog/2026-01...

echasnovski.comHow many Neovim plugins is too many – Evgeni ChasnovskiExploration of how number of loaded plugins affect startup+runtime performance

27/1/26, 4:23 pm0 reposts16 likes

Donovan Hubbard

@donovanhubbard.bsky.social

14 July

This is some great benchmarking. Honestly, even though there is a statistically significant difference in startup times, 2-3ms is not noticeable to an end user. With all the supply chain attacks going on, I’d be more worried about the risk of running 50 different plugins that could be compromised.

unintendedleap.bsky.social

@unintendedleap.bsky.social

30 Jan

Hey Evgeni! Thank you for the article. I'm curious about this bit: > consider doing some simple lazy loading (like after first screen draw or on InsertEnter/CmdlineEnter events) I understand the event part: you use autocmds for those. But how do you run something "after first screen redraw"?

unintendedleap.bsky.social

@unintendedleap.bsky.social

s/redraw/draw 😀

The way I do it is with `vim.schedule(function() ... end)`. When inside config file, it will be executed after first draw. A more convenient solution is to use `later()` from 'mini.deps'. I also plan to add a more involved function to 'mini.misc', since 'mini.deps' will retire eventually.

Evgeni Chasnovski

@echasnovski.com

27 Jan

By the way, the blog from now on should have comments powered by Bluesky. Answers for Bluesky post above (this one included) should also be shown as comments below blog post. It is powered by `bluesky-comments` Quarto extension: quarto-ext.github.io/bluesky-comm...

quarto-ext.github.ioBluesky Comments Extension – BlueSky Comments

Meni

@menisadi.bsky.social

17 Feb

This Bluesky integration into the blog's comments is neat! Is it simple to implement?

Evgeni Chasnovski

@echasnovski.com

17 Feb

With Quarto - relatively straightforward to add with quarto-ext.github.io/bluesky-comm.... Although there is friction when using, as it requires a link to a Bluesky post in a blog post. So it is: post blog -> post Bluesky -> edit blog post with a link for comments. Didn't find a smoother way :(

quarto-ext.github.ioBluesky Comments Extension – BlueSky Comments

Meni

@menisadi.bsky.social

17 Feb

Cool! Not too bad of a friction. Too bad I'm not using Quarto for my blog (using Minimal Mistakes theme via GitHub Pages, I'm a simple man)

Meni

@menisadi.bsky.social

16 Feb

Great post! Now I need to decide if I want to save those extra ms and just use mini.nvim :) Currently, I'm using a total of 57 plugins 😳

Meni

@menisadi.bsky.social

14 July

Since then, I refactor my entire config and it is now 17 plugins and less than 400 LOC (single file for now). Using the new vim.pack :)

Evgeni Chasnovski

@echasnovski.com

14 July

Nice! You can go even lower in plugin count by using 'mini.nvim' and its modules instead of at least 8 plugins you are currently using. Just saying :)

Meni

@menisadi.bsky.social

15 July

I will consider it :) [I gave my plugin-list to Claude and it claims that there are indeed 8 of them which have a mini.vim equivalent or a close alternative]