LazyVim is what kept me using NeoVim. It made reproducing a usable setup much simpler.
this post was submitted on 31 Jul 2023
33 points (100.0% liked)
Neovim
29 readers
1 users here now
founded 1 year ago
MODERATORS
Just curious why is "reproducing the setup" important to you? You need to install it on a lot of systems?
I don't know about OP but personally I run nvim on 3 systems (4 if you count termux on my phone) and it's very nice being able to test out a config and plugin updates on my personal systems before pulling down the changes on my work laptop so I know everything just works™
I don't actually use LazyVim, but I do use the Lazy plugin manager
Changing, upgrading hardware or OSs makes reproducibility a highly valuable feature of an IDE.
@jim_stark @ericjmorey personally, I'm using my neovim config on personal Mac, work Windows laptop, WSL on windows and few other Linux machines (both personal and work related). It's at least 5 devices, each with different OS. If neovim would work differently on each of them and the environment wasn't reproducible, I'd give up with neovim
I share my dotfiles repo between my MacBook and Linux pc so anything that goes in there is run on both operating systems.
Yep, that's a good reason. I guess dot files should also be downloaded from github just like extensions. Makes this stuff a lot easier.
For me, LazyVim has been the easiest to config my own way of all the configuration setups. I've used many of the other ones, and they all felt so hard to make a change with them. LazyVim just works and is easy to add to and change things around.
I had the same personal experience (compared to spacevim, doomvim and lunarvim). I just want something feature rich working out of the box, like many other IDEs... With easy access to keyboard shortcut hints. And I want to be able to customize without breaking it. So far, I have been using doom emacs. The reason is that vim didn't have a curated set of plugins that I could tinker with without being frustrated. Again, this was my personal experience with it over the years. I just kept 'raw' vim, and used many other CLI tools around it (e.g. lazygit, a python REPL, etc.)
I never picked up any of these languages to be honest.. I mean, vimscript or Lua.
Maybe if I had, my experience would have been another. I know many people that know basic vimscript prefer to have 'vanilla' config, sometimes not even using vimplug or pkg managers. And they got along better than I did with my empty vimrc ;)
I’m looking at implementing lazy.nvim, the package manager, but not LazyVim. Personally I like to be in control of everything and LazyVim takes too much away from me.
What does it take away?
For me LazyVim is just magic I don’t want to learn, along with preferring to have explicit control of the whole setup. Also migrating to something else takes more effort going from one magic to another magic. I’ve just finished migrating from packer to lazy.nvim and I like that I still have all the git history in my plugin/* files.
I’m very happy with my new “vanilla” lazy.nvim setup now.
One nice thing with lazyvim is there's a single option to disable all the key bindings so you can map them yourself. I really like the set of plugins it comes with too, so I've been really happy with the distro so far.
Yeah I like the set of plugins it comes with. It’s definitely a well curated distributions.
I learn a lot about lazy.nvim reading LazyVim documentation and config.
You can roll your own after reading the LazyVim, kickstart.nvim, astrovim, etc.
With lazy.nvim, there is little magic in nvim distros.
Astrovim community has many working config and you can reference them as a starter when you add new plugin to your config.
Yes there is definitely a lot that can be learned from those different distributions. The community around them is a big plus. While I don’t use anything magical myself, I’m happy they exist for various reasons.