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.
This reads like AI. But also doesn’t touch on the problem of running setup functions and such being very different.
@Hexarei @codeinabox
I was about to say that. Loading a plugin with it’s default config is easy (shit I did that back with Vim-Plug, while ignoring Packer because “it just works”, a couple years ago).
Just to add to it, there’s a thin wrapper around it called
zpackthat’s basically a drop-in replacement forlazy.I’m not the dev, but I’ve migrated from
lazyto 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.
