bew
commented
4 years ago Actually it doesn't look that much faster from this benchmark from vim-plug author: https://github.com/junegunn/vim-startuptime-benchmark
Using more lazyness in vim-plug could be enough to reduce startup times..
Also I need to profile my startup time to avoid useless optimizations
I already moved to a kind of custom system to declare plugins, that uses Lazy as a backend.
But want to move to https://github.com/nvim-neorocks/lz.n for loading plugins, and Nix-based install/make-available of plugins.
TODO: impl not clear exactly..
Old issue (before @2024-09-27)
vim & neovim now natively supports packages of plugins: https://neovim.io/doc/user/repeat.html#packages This seems to allow faster plugin loading on startup and simpler/cleaner (how so? native-to-vim?) plugin handling (instead of only relying on `runtimepath` mutations). The idea of `pack` based plugin managers is that the manager is a vim pack, which manages a bunch of plugins ### vim-packager https://github.com/kristijanhusak/vim-packager ### minpac https://github.com/k-takata/minpac motivation: justinmk moved to it! and it claims to be faster https://www.reddit.com/r/neovim/comments/d4rdc0/what_new_configurations_have_you_added_in_your/f0ggn6t/ Plugpac: as thin wrapper around minpac to have a near vim-plug experience: https://github.com/bennyyip/plugpac.vim (what about compatibility of