Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LazyVim

lazyvim.org

Post reply on HN
Print view View original

461–470 of 537 posts

Re: LazyVim

#461

Post by DropInIn »

nextlevelwizard wrote: post #157
p-e-w wrote: post #87

Earlier quoted context omitted.

> The amount of work needed not only 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. "This airplane is the choice of professional pilots! The first thing we advise you to do is turn the y…

More that you want to carve a bowl out of wood. Vim is like a knife that with some modifications you can turn into a carving knife. VSCode is like a chainsaw that has attachments that have been made for it and it also has bowl carving attachment. If you don't know your tools, then you can easily mess the knife modification and not end up with a carving knife. The chainsaw with ready made attachments is way easier to…

Nah vs code is a multitool with both a hook blade (the knife younuse for carving out a bowl) And a chainsaw....

Slightly more unwieldy in that specific narrow use case than a plain hook knife but you don't need a second tool to cut the log you take the wood for the bowl from...

In other words, it's a tool that let's you do near anything with minimal modifications whereas vim is a tool that requires significant modification just to do Any task other than looking at it.

Re: LazyVim

#462

Post by DropInIn »

yjftsjthsd-h wrote: post #142
danjac wrote: 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…

> The amount of work needed to get a basic IDE up and running for your languages of choice, I don't think vim is meant to be an IDE. If you want an IDE, go get an IDE. If you want a text editor, vim works well. But vscode is unwieldy as a text editor, and vim is painful to contort into an IDE.

Then tell the vim fan bois to stop telling people to use vim as their ide....

The issue isn't with the fact people try to use it that way, it's that those who use vim are adamant it's the best option for doing so and berate the Other until they try.

Re: LazyVim

#463

Post by 3836293648 »

JeremyNT wrote: post #402
noud wrote: post #132

Am I the only one using vanilla vim with a minimal configuration file ( Very easy to setup. Moreover, when I'm on a different computer and open (vanilla) vim without any configurations. I know that everything is more or less the same as my default vim environment. I think it's not that hard to learn developing in the default vim environment, with some minor tweaks. Also related, How to Do 90% of What Plugins Do (With…

I worked this way for ages, but over time I came to appreciate some modern IDE-like conveniences like linters (I use ALE for this stuff). Especially thanks to LSP (which neovim supports natively, though I stick to upstream Vim myself) you can get a lot of value from these. I think it's easy to go overboard though. A lot of plugins (and these meta-plugins) provide little value over what vim can do on its own with a li…

Neovim isn't exactly downstream. It's a hard fork from ten years ago. They've gone their separate ways for a long time

Re: LazyVim

#464

Post by cempaka »

tambourine_man wrote: post #430
jstanley wrote: post #335

Earlier quoted context omitted.

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.

Oh no, I need at the very least timeoutlen, visualbell and line number. I type that manually when I SSH if I must. Don't want to wait for ESC, no beeps at all and I wanna know where I am on the document. And lots more is needed for decent Vim IMO. smartcase, set hidden, etc.

relativenumber is essential too, unless you like typing something like d-638--G just to delete 15 or 20 lines of text.

Re: LazyVim

#465

Post by pacomerh »

I have been using Lua to customize Neovim for some time now and generally, the experience has been good. From time to time, I do encounter issues such as dependency incompatibilities butI always manage to find a solution. Recently, though, I experimented with LazyVim, and I must admit, it might replace my current setup. LazyVim fulfills all of my requirements, it works and looks great.

Btw, if you this is your first trying it check out Elijah Manor's video: https://www.youtube.com/watch?v=N93cTbtLCIM

Re: LazyVim

#466

Post by wredue »

majkinetor wrote: post #188
CiTyBear wrote: post #179

Many people complain about the time you need to have a proper vim. In computer security, I learnt to make my own tools, to develop my own script that match what I want to do/scan. For vim, this is exactly the same. I started with Python so my vim became the best Python IDE (for me) and that's all. What I said to junior dev is "Here my vim conf, you are allowed to copy/paste only what you understand". Then I did some…

Indeed, yet I switched to vscode after 10 years of vim because it is next in line to vim when powerfull editor is in question, and once you set it up you can have it 0 on-boarding everywhere else working on ANY machine you use, including browser. I use a lot of machines and I want my editor with me. Its mind blowing that you can just login in GitHubs vscode within a web browser on any repository and have your own vsc…

I mean. Helix is a pretty decent editor with a nice set of defaults over vim.

Not as customizable. But I pretty much would configure vim to do what helix does out of the box anyway.

Re: LazyVim

#467

Post by troyvit »

Shorel wrote: post #453
troyvit wrote: post #442

Earlier quoted context omitted.

This sounds like a refutation, but it's also in the same spirit as the parent. "No need to deal with insane complexities, I'll stick with my simple editor." Whether that's vim or Sublime, that answer works, and that's pretty cool.

Except that ST is not "simple" by any measure. It uses the standard bindings I learned with Windows decades ago, and builds on that. Vim forces me to change it all to the vim-like model. It's about having to learn a new set of key bindings just for that program alone.

That makes sense, and I definitely wasn't trying to denigrate ST. Having not touched Windows since 2003, and having come from the vim world I had to learn a few aspects of Sublime to help my coworkers out, and just like you say, having to learn a new set of keybindings was a pain.

Re: LazyVim

#468

Post by majkinetor »

masukomi wrote: post #416
altonas wrote: post #271

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.

The thing about vim and emacs is that both of them, out of the box, suck. BUT, what they both offer better than anything else, is the ability to gradually modify them to match what your brain needs. I 100% agree with your hyperbolic "200 keybinds to make a view component" But that's ...that's not how it works unless that's what your brain wants. With ALL editors you eventually encounter "ugh, this is frustrating" or…

Exactly. You absolutely need maximum configurability for the most important tools in your arsenal. You can pass with defaults on less used tools but everyday stuff should be as efficient as possible. In my case those tools are editor, shell, browser, OS, media player - they are customized extensivelly.

Re: LazyVim

#469

Post by eikenberry »

_7tgr wrote: post #126
eikenberry wrote: post #102

Earlier quoted context omitted.

An alternative to Neovim or VScode that might be worth checking out is Helix ( https://helix-editor.com/ ). It is a Vim/Kakoune inspired editor that is really starting to hit its stride. I haven't used it extensively yet, but I'm testing using it for development now and am thinking of switching to it full time. It maintains the minimalism of (Neo)Vim while coming with a great builtin setup like VScode. To get a feel…

Helix is interesting but I don't really gel with its editing language (subject + verb instead of verb + subject like (n)vim's). Happy to discuss what I think is lacking in more detail, but basically: the premise of 'you can see what you're about to operate on before you do the action' is satisfied for me by visual mode, and I like macros better than multiple cursors. So I don't want a (subjectively) less efficient ed…

I've seen that breakdown before and have skimmed it but didn't really find an analytical breakdown of why style X is better/worse than style Y for person Z very useful. Tools preferences are to personal and varying. It really depends on how it meshes with your style and the only way to really test that is to try it out.

Re: LazyVim

#470

Post by hju22_-3 »

globular-toast wrote: post #149
p-e-w wrote: post #87

Earlier quoted context omitted.

> The amount of work needed not only 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. "This airplane is the choice of professional pilots! The first thing we advise you to do is turn the y…

Let's not forget that vim isn't really designed to be an IDE, though. People just like the editor so much they want an IDE with it. Unfortunately using vim itself for that is the wrong choice. The correct choice is emacs with evil mode.

The correct choice is to instead use something that doesn't require a really long time to both learn properly and modify until it's decently functional, even including premade distributions for it, and just using something to get the job done so that, you know, you get the job done instead of preparing to get it done and not getting it done.
Post reply on HN