4 ms·
On the neovim subreddit one of the core maintainers said that relying on users to lazy load plugins is an extremely poor practice and something that should be d
by azemetre 1y ago
On the neovim subreddit one of the core maintainers said that relying on users to lazy load plugins is an extremely poor practice and something that should be done by the author's of said plugins. It is just a matter of how you initialize your plugin/name-of-plugin.lua file.
Don't know if it helps but I recently migrated to vim.pack. With another neovimmer he helped me create a defer function and pack update. The only plugin I initially load is a dashboard while deferring everything else. Brought my startup time to sub 100ms.
https://github.com/azemetre/dotfiles/pull/61/files https://github.com/azemetre/dotfiles/pull/61/files
- shmerl 1y agoI don't understand that argument (and I've heard it several times), see comment below about plugins dependencies. I.e. that argument is OK for isolated cases, not for more complex dependency graph.
- azemetre 1y agoThis is the reddit thread where the lead of the project talks about it: https://www.reddit.com/r/neovim/comments/1n2nax0/why_vimpack_was_based_on_minideps_but_not_lazynvim/nbc9wsl/ https://www.reddit.com/r/neovim/comments/1n2nax0/why_vimpack... It doesn't answer your question about plugin dependencies (although vim.pack lets you handle this), but it might give you more insight on where vim.pack will go in the future.