Live data from Hacker News

LazyVim

lazyvim.org

71–80 of 537 posts

Re: LazyVim

#71
post #68

Earlier quoted context omitted.

I had luck using gnu stow to switch configs easily too.

Hadn’t heard of this. Thanks. I guess there are probably plenty of little GNU utilities out there that just haven’t hit their deserved mindshare yet

https://kkovacs.eu/cool-but-obscure-unix-tools/

Re: LazyVim

#72
A true IDE layer for neovim.

The best part is that the developer(Folke) is very active with development and basically helping with all sorts of problems- the other day, I opened a pull request and it was resolved within hours..

Thank you Folke for the amazing work around neovim not limited to lazyvim.

Re: LazyVim

#73

I feel like I should be the kind of person who prefers eMacs over vi(m), because I've always been a hotkey maniac. I'm actually not though at all, and I much prefer the simplicity of vim. I already have way too many hotkeys lingering in my brain, especially since I played the game Age of Empires II. I don't play many games these days, and I certainly don't use their hotkeys (I play exclusively on consoles these days,…

Stick with what you like, if it works for you then that's what's most important. Personally I switched from neovim to emacs, but I don't care for the 'emacs style' of keybindings. Instead I use evil-mode and set my own bindings with hydra for everything else. Tbh main reason I switched was elisp envy; there's not really a whole lot that you can do with one but not the other.

Re: LazyVim

#74

Earlier quoted context omitted.

At least for me, Vim is immediately useful, and I rarely do much personalization. I agree that personalization is not an adequate measure of an editor. I don't agree that the problem with IDEs has anything to do with personalization. At least for me, it boils down to wanting an editor for text, rather than some specific programming language or environment. Traditional IDEs have been very "project" focused which isn't…

> a master carpenter master carpenters produce artisanal works. those works are valued for the craftsmanship itself rather than the utility. so it makes perfect sense that master carpenters would be incentivized to put thought and care into their tools. me? i'm just a tradesman/laborer. okay not really but there's still no such thing as "artisanal software", at least for sure where the code itself has intrinsic value…

Ever try to cut wood with a dull blade? I really don't recommend it. Even a novice carpenter will benefit from taking care of his tools. Admittedly it's more important for carpenters because blunt tools can get you injured. Excepting RSI issues, the worst that will happen with a suboptimal text editor is very marginal inefficiency (typing probably isn't the bottleneck anyway.)

Re: LazyVim

#75
After using vim for more than a decade and slowly acquiring my personal config I switched to lazyvim. No regrets.

Also for simple chores like mass converting your config from vimscript to lua I'd really recommend bing chat, an LLM with the docs loaded works wonders on it, getting all my stuff ported and lazyvim set up took less than an hour IIRC

Re: LazyVim

#76
LazyVim got me back into vim. After years of custom configs and/or heavily editing lunarvim and nvChad I was getting a bit burnt out but decided to give lazyVim a try, and I was absolutely blown away. For the first time a vim setup actually felt like a real IDE. It took about 60 seconds to go from having lazyvim installed to having a fully functional IDE that I could use at work in a real environment. That's the same amount of effort it would have taken me to set up a fresh install of vs code with whatever plug-ins I wanted.

If you've ever been put off by the complexity and setup of nvChad or lunarVim, then I highly suggest giving lazyvim (or astrovim, its similar but with more "batteries included") a try

Re: LazyVim

#77

I know it sounds like a pain, but I really am a big advocate for learning how to customize vim (or emacs) yourself. These are great places to start, but the power of terminal editors is that they cater to you at a very personal level. The problem with "IDEs" isn't that they are bulky, it is that they railroad you into doing something a very specific way. Terminal emulators put the custom configuration in your face be…

I use lazyvim and you're still going to be configuring a _lot_ of stuff by hand with it. It's really just a framework for configuring neovim with an opinionated file structure. Compared to other neovim plugin 'distributions' this one is pretty hands off as far as out of the box config--it really just has the bare minimum to get popular language LSPs up, and a lot of missing LSP features that neovim hasn't implemented…

Probably what I like about my NeoVim setup (an organic, home-grown completely from scratch mess of .vim and .lua files) the most is universal containerized language server for any project.

It gets me go to definition, peek definition, etc. in TypeScript, Python and probably anything else LSP-compatible without polluting my main machine with any of those development environments and only requires Docker.

The editor detects a special INI file in project directory and launches a Docker container that runs a language server. The INI file can specify a common Dockerfile (works for zero-install Yarn where it mounts repository root as read-only volume and just works(tm)) or a project-specific Dockerfile that does some system setup (useful in case of complex Python/Django backends, for example).

I’d be curious to try a configuration like LazyVim if it supported something like that out of the box, but last time I checked most of these were written in mind with LSP running directly on your host.

Re: LazyVim

#78
I've been using vim for years, switched to neovim, and at this point I'm ready to throw in the towel and just use vscode for anything beyond simple text editing.

The amount of work needed to get a basic IDE up and running for your languages of choice, even for commonly used languages such as Python or Javascript, is far too much for someone who wants to get on with their day job or hobby coding and doesn't want to spend precious hours fixing obscure issues in Lua.

Furthermore, the community does not have a good culture of documentation and learning: too many plugins have very sparse docs, and other online resources such as the Neovim subreddit are hostile to newcomers with "RTFM" a common answer. The community is also fragmented, with too many ways to do the same thing in the name of some platonic ideal of personal freedom over practicality.

A simple question like "How do I set up Black with neovim to format my Python files on save?" will yield a dozen answers, each one with someone's favourite plugin. Setting up that plugin will require another plugin, and so on until you end up with a Jenga tower of dependencies that doesn't quite work the way you want, but is too fragile and time-consuming to tweak correctly.

In the meantime, I can just Ctrl+P and install what I need in vscode and be on my way in a few minutes.

I don't particularly like vscode. It's heavy and slow and janky, particularly on older laptops. I don't like being sucked back into the Microsoft ecosystem after spending years getting away from it. But ultimately, I want to just get on with my job, and my job is not Lua Developer or Neovim Plugin Expert.

Re: LazyVim

#79

I feel like I should be the kind of person who prefers eMacs over vi(m), because I've always been a hotkey maniac. I'm actually not though at all, and I much prefer the simplicity of vim. I already have way too many hotkeys lingering in my brain, especially since I played the game Age of Empires II. I don't play many games these days, and I certainly don't use their hotkeys (I play exclusively on consoles these days,…

I've had several people recommend me their IDEs or some new text editor from time to time by telling me that the editor supports Emacs style keybindings assuming that is the main difference between editors. I've never used emac's native keybindings, nor do I use vim's since I don't use qwerty.

While my custom keybindings are something I would not want to give up they can be replicated in any other editor that provides this basic functionality. What cannot be replicated is the whole reason why I prefer emacs, I like being able to use it like a file explorer, like a terminal, I like being able to open or edit pretty much any type of file I ever use. When you combine the ability to work/view most of the files with consistent keybindings, that is the killer feature that emacs provides, its never been about the keybindings.

I'm curious though, I never really got into vim as soon I realized that it only makes sense if your layout is qwerty. Is vim just its keybindings? or is it like emacs in that the keybindings are not the main reason people use it?.

Post reply on HN