4 ms·
I'm torn. I really like Lazy and have never minded having different package managers for Vim over the years. But having one blessed one is probably better lon
by dismalaf 1y ago
I'm torn. I really like Lazy and have never minded having different package managers for Vim over the years. But having one blessed one is probably better long term, just like built-in LSP and Treesitter.
- shmerl 1y agoI agree if it at least can match lazy.nvim in features, which it so far doesn't. Stuff like pinning plugin versions, notifying about breaking changes and actual lazy loading are very useful.
- 3836293648 1y agoIt feels a bit dishonest to criticise an unreleased development build for a lack of features
- shmerl 1y agoI'm not criticizing it, just describing what I'd consider a level good for switching at least for me. It can be different for others and they might think they need less.
- porridgeraisin 1y agoIt has pinning already > Freeze plugin from being updated: > - Update 'init.lua' for plugin to have version set to current commit hash. You can get it by running vim.pack.update({ 'plugin-name' }) and yanking the word describing current state (looks like abc12345). > - :restart.
- shmerl 1y agoThat's good
- azemetre 1y agoI recently migrated from lazy.nvim to vim.pack and it was way easier than expected: https://github.com/azemetre/dotfiles/pull/61/files https://github.com/azemetre/dotfiles/pull/61/files I followed the work of another neovimmer where he was able to replicate deferring with vim.pack. Brought my startup time down to sub 100ms. Definitely worth it to me as it's one less "core" plugin to maintain. Having things like telescope or trouble are one thing, it's quite another to rely on a plugin that changes the way neovim interacts with loading.