Neovim 0.12's Built-in Plugin Manager — Should You Ditch lazy.nvim?
2mon 18d ago by programming.dev/u/codeinabox in neovim@programming.dev from samuellawrentz.com
The Deal-Breaker
vim.pack has no event/filetype/command-based lazy loading. None. You either load at startup or you manually call :packadd in your config yourself.
Oh, so it’s sane and doesn’t try to bullshit it’s way out of plugin authors’ incompetence?
I’m sold!
It successfully protects us from authors not including lazy loading, why is that bad?
It doesn’t, it shifts responsibility at best.
Just to add to it, there's a thin wrapper around it called zpack that's basically a drop-in replacement for lazy.
I'm not the dev, but I've migrated from lazy to it without much of a hassle, and the performance seems to be on par. I did encounter a bug, but the dev was quick to fix it. Just wanted to give them a shout-out.