7 ms·
I feel like I have to migrate to a new (Neo)Vim package manager about once every 3 or so years. I think my path has been: pathogen -> Vundle -> vim-plug -> lazy
by bikeshaving 1y ago
I feel like I have to migrate to a new (Neo)Vim package manager about once every 3 or so years. I think my path has been: pathogen -> Vundle -> vim-plug -> lazy.nvim. Hopefully, this the last VIM package manager?
- trip-zip 1y agoPlug still gets the job done imo. But I'm also hopeful that since this one is builtin to the language it'll likely be end-game worthy for lots of users. I have tried it out and had a painless experience though I never did anything fancy like lazy offered.
- jauntywundrkind 1y agoLazy.nvim seems pretty triumphant. But yeah a lot of others are also supported by various plugins. Some unity would be nice, abstractly. But man, it's hard to have faith we're going to get as anything good fast and reliable as lazy.nvim. it could happen though!
- Lio 1y agoEvery plugin manager I've used since Pathogen has seemed "triumphant" at the time. I think they've all been reliable enough and everytime I think well this will be the last time I change that. I currently have a Packer config on one machine and Lazy on another and honestly don't know why I bothered switching to Lazy. What I really crave is simplicity so if NeoVim builds every thing in I think it will be good enough for me.
- Nilithus 1y agoI switched from packer to lazy after I noticed the maintainer of packer stopped using packer in his neovim config. Also I believe he has now officially marked it as unmaintained and recommends lazy or pckr
- f311a 1y agoNew package manager is pretty slow right now, it's like 200ms to load nvim with lazy vim vs 1 sec with Pack.
- christophilus 1y agoHow many plugins do you have?
- f311a 1y ago22
- yoyohello13 1y agoLuckily this is the built in, official, blessed one. So it’s likely going to be the most widely supported and available. (Maybe not most feature rich though)
- film42 1y agoI think I update Vundle like once every 3 years.
- rapind 1y agoI’m literally just using git with vim.
- gitaarik 1y agoHow do you keep your plugins up to date?
- t_mahmood 1y agoDon't know about op, I had a script that would go through each plugin folder, check if it was a git folder, and pulled. Now I use vimplug though
- porridgeraisin 1y agogit submodule update
- t_mahmood 1y agoHmm, when I set it up, mercury was a thing, so, the script handled both. And, also, I was young, and that made me feel good :D
- bayesianbot 1y agoAm I the only one who thinks the way plugins are updated in lazy.nvim (and probably others) is a bit insane? It seems to just pull the latest commits. Every time I update, I feel one rogue commit away from someone stealing my keys. It definitely feels like the riskiest thing I do on my system. Or have I misunderstood something?
- gitaarik 1y agoSo you mean you review all the plugin code before you add it? And when there's an update you review the changes?
- 0x457 1y agoI started using nixvim. I think I gave up around vim-plug. Trying to maintain reliably working config across multiple machines and OS was a nightmare.
- colordrops 1y agoNixvim is great. I got it configured with a flake and add it to all my machines. Nix lang is really suitable to composing neovim config.
- 0x457 1y agoYup, I have a giant flake that configures all of my home linux and macos machines. Every machine gets more or less the same home-manager configuration applied, nixvim is split into its own flake.
- schonfinkel 1y agoI've been using the "old school" approach of just leveraging neovim + huge list of `vimPlugins` in my Nix config, makes you about the myriad of package managers for vim/neovim. Replacing it with nixvim is on my forever growing todo list.
- naniwaduni 1y agoI tossed pathogen in favor of git submodules in ~/.vim/pack/*/start/ in 2017 and it's still like that.
- rand0m4r 1y agosame here - works great and never needed anything else.
- freedomben 1y agoSame. I love vim and have no plans to leave, but I have no interest in being on the upgrade treadmill when my current system isn't broken. I've also had plugin updates break stuff, and it's a simple rollback in git back to a working state. I'm not sure how hard that is with these various plugin managers, but it's quite simple with git and I don't have to learn yet another tool/way of doing things.
- sbinnee 1y agoI have been staying on vim-plug where everyone seems to be moving on to lazy.vim. I was considering a weekend to migrate to lazy.vim sometime. But with this news, I might just have to wait for this plugin manager to drop.
- ComputerGuru 1y agoWhy? I’ve been using dein since it was released and haven’t needed to switch to anything (though I’ve noticed the momentum shifts quickly between different ones).
- lawn 1y agoThis is the FOMO speaking. You don't have to switch if you don't want to.
- bravetraveler 1y ago+1. Configured my plugins years ago and have not cared about the mechanism at all. I might even have confused things and landed on two. Whatever. The result is what matters: I have extensions. In the exceedingly-rare event I do want to add one... overwhelmed with choice. "Have to" is entirely self-imposed
- Aissen 1y agoJust looked at my (private) dotfiles git history - pathogen in 2011 - vundle in 2013 - vim-plug in 2017 Haven't moved since, Plug still does the job, even after I moved to neovim in 2021. Will probably move to the new built-in package manager once the dust has settled.
- motiejus 1y agoin Nix it's the same for as long as I remember, both on NixOS and nix-managed home-manager on MacOS and Linux: neovim = { enable = true; vimAlias = true; vimdiffAlias = true; defaultEditor = true; plugins = [ pkgs.vimPlugins.fugitive pkgs.vimPlugins.fzf-vim pkgs.vimPlugins.vim-gh-line pkgs.vimPlugins.vim-gutentags pkgs.vimPlugins.nvim-lspconfig pkgs.pkgs-unstable.vimPlugins.vim-go pkgs.pkgs-unstable.vimPlugins.zig-vim ]; extraConfig = builtins.readFile ./vimrc; extraLuaConfig = builtins.readFile (pkgs.replaceVars ./dev.lua { inherit (pkgs) ripgrep; }).outPath; }
- burnt-resistor 1y agoSimilar here too. I'm on the lazy.nvim train too because it's componentized, powerful, and scalable. It would take me ages to get all of the stuff going that Just Works™ (pretty much) OOTB. Yes, even Copilot if you're into that sort of kinky code completion sharing with OpenAI/Microsoft everything you type.
- azemetre 1y agoI recently moved away from lazy.nvim to using vim.pack. You can check out my PR here: https://github.com/azemetre/dotfiles/pull/61/files https://github.com/azemetre/dotfiles/pull/61/files It was worth it to me because I never relied on many features of lazy.nvim. The benefit of the approach linked in the PR is that it also defer's loading packages as well. The only one I initially load is alpha.nvim (a dashboard), everything else gets deferred. This brought down my startup time from around 300ms to sub 100ms.
- theflyinghorse 1y agoYou're using an editor that is built to be configurable for people who enjoy endless configuration. This will not be the last config manager. You might as well ask JS community if Nextjs is the last JS framework
- amelius 1y agoYeah, this is like asking if "uv" will be the last package manager for Python.