Live data from Hacker News

LazyVim

lazyvim.org

471–480 of 537 posts

Re: LazyVim

#471

Earlier quoted context omitted.

Agreed. Back then, I tried to get into neovim with packer and a ton of plugins, then tried AstroVim and stuff broke all the time. Went back to vscode. I tried it again about half a year ago with a much leaner, custom lazy (plugin manager, not LazyVim) setup, and now it's my main IDE for everything except C++ (clangd sucks, sorry) It took me less than a day to get a decent config, and now I rarely touch it (occasional…

What do you use for C++? I was planning to integrate clangd into my setup soon.

I've had a good experience with ccls, although to be honest I haven't really compared it with clangd so I can't say if it is actually any better!

Re: LazyVim

#472
post #400
post #275

Earlier quoted context omitted.

The problem is that Vim can be used to create config files and source code files among other things. VS Code can be used for very much the same things. The output of both tools is practically the same thing. The niche of things Vim can do and VS Code can't is tiny and constantly decreasing.

You can run Neovim on a remote server through ssh. I think that's the main difference

VSCode can do that with the remote extensions.

Re: LazyVim

#473
post #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 sp…

this is basically why I moved to https://github.com/helix-editor/helix/ for most things. neovim setup is a nightmare these days. 0.5 introducing Lua was both great (yay! vimscript sucks!) and horrible (oh no, everyone took this power and made a full operating system worth of complex stuff out of it that rarely fits together cohesively, and it all updates so frequently now that I can't keep up)

I don't actually think it's Lua's fault. And I don't necessarily want to jump and say "the improved accessibility of this thing turned it into an unusable circus", because that's both unnecessarily sassy and also likely prescribing blame in some places it doesn't fully belong. But there's something that tidally changed in that time, and especially in the past 2-3 years, my vim setup became a thing I dreaded updating (because it would 100% guaranteed, every time, break something about my workflow)

Re: LazyVim

#474
post #159
post #151

Earlier quoted context omitted.

You mean the one with syntax highlighting disabled by default?

Yeah. I actually find that no highlighting in some ways helps you understand the language better. Because you have to parse it, not rely on the highlighting to do it for you. When I was learning Rust, I spent a year writing Rust in vanilla vim which is by some accounts insane. But I did it for the uh immersion. And I’m happy with the result. I do use Zed for working on projects when on my home turf. It’s just that I’…

Related prior discussions on this topic:

- https://news.ycombinator.com/item?id=12886067 - https://news.ycombinator.com/item?id=23902124

Re: LazyVim

#475

Earlier quoted context omitted.

This is why I switched to Helix. The configuration is practically non-existent, and it has default configs for all the language servers I could ever want to interact with. I just put the language server binary in my path and I'm ready to go with autocomplete and all the other features.

I've also switched to Helix recently and I get the feeling that is not emphasized enough how much it is about having default integrations for modern standards like LSP, Tree-sitter, and DAP. It's amazing how much functionality you get with just that and not having any plugins or complex configuration.

I actually dread the day Helix eventually gets the WebAssembly plugins system that's been floated around. The current Helix culture of "you get a Kakoune-like editor that can do three categories of "bonus" things, and NOTHING ELSE" encourages a more manageable pace of development (and maybe more importantly: slower updates for those of us exhausted of software churn breaking our stacks constantly), and discourages feature creep/bloat. I love where Helix is at currently. After some tinkering and adjusting a few keybinds, and after a few releases for them to fix various bugs I'd been dealing with, it's quickly become my new favorite editor, and has nearly fully replaced NeoVim. Hats off to Helix.

Re: LazyVim

#476
post #266

Earlier quoted context omitted.

Would you mind sharing it? Im just getting to grips with vim so any pointers towards some simple improvements would be much appreciated.

Sure: set ts=4 set sw=4 set softtabstop=4 set expandtab set hlsearch set incsearch set wildmode=longest,list OK, only 7 lines then :) Basically: tabs are 4 spaces, searching works better, and tab completion works like bash.

Thank you!

Re: LazyVim

#477

Earlier quoted context omitted.

Can you actually explain how it's suboptimal UX, and what I could be doing better. I want a simple IDE, not suboptimal bloat. I don't need 200 keybinds to make a vue component. Just because you have a bunch of custom quirks doesn't mean that I do.

Any time somebody else creates something instead of you, it must be accepted as suboptimal. We are all unique human beeings and have different kinds of habits and disfunctions, levels of knowledge etc. so 1 setup for all is pretty much impossible and nobody else can do it but you. Any time you accept that, you are accepting suboptimal UX. If you are doing so you are admiting that you are either lazy, or you are good…

Cant wait until you create your programming language to use in the company you created racking up the optimal millions while laughing at us lazy slobs!

Re: LazyVim

#478

Earlier quoted context omitted.

Any time somebody else creates something instead of you, it must be accepted as suboptimal. We are all unique human beeings and have different kinds of habits and disfunctions, levels of knowledge etc. so 1 setup for all is pretty much impossible and nobody else can do it but you. Any time you accept that, you are accepting suboptimal UX. If you are doing so you are admiting that you are either lazy, or you are good…

Cant wait until you create your programming language to use in the company you created racking up the optimal millions while laughing at us lazy slobs!

You can stop immediatelly.

Re: LazyVim

#479

Earlier quoted context omitted.

Cant wait until you create your programming language to use in the company you created racking up the optimal millions while laughing at us lazy slobs!

You can stop immediatelly.

Maybe YOU should stop calling other people lazy for something actually very productive, aka not wasting million hours tinkering with lua for marginal returns over investment, often on company time…

Re: LazyVim

#480
post #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 sp…

I dont know.. The argument i read all the time is "i don't want to invest time in vim". But what kind of professional spends hours uppon hours learning his craft (programming), but is unwilling to invest some of those hours into mastering professional tools? What about sharpening the axe? The amount of time i saved by sticking to vim is definitly more that the time i needed to learn it.. IDEs are easy mode and waste…

Some hours is not what one should put into Vim, IMO. I've used it for many years and felt I got better at it very gradually (maybe I'm like that with most things). It's much more than hours! It's using it every day for a few years :)

To honor the many-years of vim, I relearned a new vim feature now: using :g to run a macro like this: https://stackoverflow.com/a/5292858

Post reply on HN