Re:Vim: So long Pathogen, hello native package loading
by egwynn on Friday October 21, 2016 @10:20AM
(#12760639)
Part of the issue is that vim’s ages-old plugin model uses a really unusual and frustrating architecture. I think the purpose here is to make the baseline package system cleaner, so that more advanced package management systems don’t need to reinvent the wheel so much.
Re:Vim: So long Pathogen, hello native package loading
by joemi on Friday October 21, 2016 @11:00AM
(#12760979)
Personally, none of the bullet points you mentioned matter to me at all, so I'm glad about the improved native package loading. Plus, I've always found it weird to need a package in order to load other packages (in a remotely sane way).
As your comment implies, vim's improved package handling is still pretty simplistic compared to some existing plugin managers, so there's really no reason _not_ to want the functionality in vim. It's not like it was a huge addition to the code that's now slowing down your system, or messing up existing plugin managers. Similarly, it's not going to cause fuller-featured plugin managers to cease further development.
Re:Vim: So long Pathogen, hello native package loading
by eridius on Friday October 21, 2016 @04:40PM
(#12764533)
On-demand loading is useful, because it speeds up launch time. You could have hundreds of packages installed, but if they're all on-demand, launch can still be blazing fast.
Re:Vim: So long Pathogen, hello native package loading
by joemi on Friday October 21, 2016 @09:29PM
(#12766462)
I think you're missing my point. I wasn't arguing against more feature-filled package managers. I was answering cjhveal's genuine curiosity about why you'd really want native package loading in vim.
- Declarative configuration suitable for version control.
- Parallel installation/update.
- Run scripts or makefile on install/update.
- On-demand loading based on open filetypes.
[0]: https://github.com/junegunn/vim-plug