Only reason I switched was I was redoing my neovim config in lua. Almost all the lsp examples are in lua and most lua plugins showed packer config examples. So I went with the kids path of least resistance and used what seemed most popular at the time.

[–] clmbmb@lemmy.dbzer0.com 1 points 1 year ago

This happens all the time with new projects. And yes, I know neovim is not that new anymore, but its development is still very active and a lot of things change, so the whole ecosystem around it will change. This will stabilize in a few years and we'll have fewer and more stable plugin/package managers.

[–] hallettj@beehaw.org 1 points 1 year ago (1 children)

When an ecosystem is new there is a lot of design space to explore. No one knows what the best ideas will be - the only way to find them is to try lots of things. After a while it becomes clearer what the good ideas are, and things settle down. That happened in Javascript when React and Vue became popular. You didn't see a new application framework every month anymore - at least not ones that got a lot of adoption. Exploration shifted to stuff like state-management libraries to use within React. Of course the search for better ideas never stops completely...

[–] __lb__@feddit.nl 1 points 1 year ago

I’ve been updating my plugin managers for over ten years now. Would be nice if neovim just bundled a default plugin manager you could use and all the examples could use.

[–] Hexarei@programming.dev 2 points 1 year ago

Bah, I just started using Neovim a few months ago and finally got my config what I thought was a good place, haven't edited it in a couple weeks, thought I was doing good.

Now I've gotta look at moving everything into something else. Fun.