Does anyone know what’s the ground they want to make a builtin plugin manager? Did they think there should be some sort of standard?

>Problem: > >New users must look for a plugin manager and figure out how to install it. > - Nvim documentation should be able to give a one-liner to install (non-builtin) plugin managers and plugins. > > Lack of a declarative way to specify plugins. > - Lets Nvim reason about dependency ordering / transitivity. > - Lets crawlers build a package index. > - [packspec](https://github.com/neovim/packspec) adds potential to leverage NPM tooling (and possibly infrastructure).

https://github.com/neovim/neovim/issues/20893#issuecomment-1...

I find it weird to not have one, given the ubiquity of plugins in (neo)vim. These editor are self-proclaimed "super easy to extend/program", until now it was awkward to need a third party plugin manager to "extend" them (the vast majority of people use plugins and don't extend all the functionalities with their own code). Plus 0.12 is said to be "The year of Nvim OOTB": https://neovim.io/roadmap/

A neovim plugin manager is essentially a git clone tool that knows how to execute a setup function. This aspect of plugin management is the same for all plugin managers in neovim. The goal is to have something that mostly works as-is but other plugins managers can potentially build off of to support advanced features like lazy loading.

They're trying to improve "setup experience" - see https://m.youtube.com/watch?v=Nq2T28_ILxc (I forget the timestamp and exact phrasing)