How does NeoVIM 0.12 and the release of vim.pack affect the future of this plugin manager?

[alerque]

With yesterday's release of NeoVIM 0.12 there is now a built in plugin manager vim.pack. I searched the issue tracker and discussions and don't see any discussion at all it here, whether any parts of it will be leveraged or if some parts of this might be obsolete or is the plan to just live in separate castles (nothing necessarily wrong with that of course) or what? Is there discussion somewhere I missed?

I'm trying to evaluate which if any plugins I should start migrating. I currently have ... count em ... three plugin managers active already and need to candidate a bit. If somebody has done a side by side comparison or discussed development plans in light of the changing landscape that would be useful to know while evaluating.

[mrcjkb]

Hey 👋

vim.pack is a minimal plugin manager that supports fetching plugins from git forges.
It does not influence our efforts in the development of lux.nvim (Issue: #539, Draft PR: #644).

• It may or may not be useful to bootstrap lux.nvim - We'll have to investigate that.
• The Nvim core team have discussed the development of a pkg.json (or "packspec") standard for use by vim.pack, to address things like automatic dependency management.
  We have written down some thoughts on it and how it affects rocks.nvim/lux.nvim on this wiki page.