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

361–370 of 537 posts

Re: LazyVim

#361

Post by distcs »

sidibe wrote: post #285
distcs wrote: post #248

Earlier quoted context omitted.

Ctrl+C and Esc do not behave the same in all contexts. The correct replacement for Esc is Ctrl+[. What if you need to type `jj`? Not uncommon to do so while writing math or physics papers. a_{jj}

Spacemacs defaults to fd, I don't think I ever accidentally left insert mode with that. Happy vscode user these days. If I find myself fiddling with an editor it's a huge red flag to me that I hate what I'm working on.

I still don't understand how these mappings are good.

What if you need to type "fd" in insert mode? Like fd0, fd1, etc. Isn't that going to be a pain? Do you never have to type "fd"?

Re: LazyVim

#362

Post by wheresmycraisin »

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…

Strange, the only thing I need to do to get everything I need these days for a new language is install the right LSP provider and point vim to it. It used to be much harder, now it's closer to trivial.

Re: LazyVim

#363

Post by thiht »

johannboehme wrote: post #359
thiht wrote: post #280

Earlier quoted context omitted.

> I don't like being sucked back into the Microsoft ecosystem You’re not though, there’s no lock-in.

but there is. VSCode core may be open source, but the plugin marketplace certainly isn't. So if you for example use VSCodium, you don't have access to the plugin marketplace and eather have to use an alternative or manage your plugins completely manually on the filesystem.

So what? You use the plugins available on the platform you use, that's standard practice. Would you complain Sublime Text plugins are not available on VSCode? Or emacs plugins are not available on vim?

This is not lock-in, just a different feature set.

Re: LazyVim

#364

Post by thiht »

goku12 wrote: post #315
thiht wrote: post #280

Earlier quoted context omitted.

> I don't like being sucked back into the Microsoft ecosystem You’re not though, there’s no lock-in.

They are certainly still trying. I used vscode a while ago. Some of the best and most essential extensions like LiveShare and Remote are proprietary and worked only on the proprietary build of vscode (the last time I checked) and wouldn't work on OSS builds like vscodium (why though?). Both these extensions and the proprietary build of vscode come with telemetry that's either opt-out or always enabled. They nudge you…

It's not lock-in, it's feature differentiation. Other platforms are free to develop their alternatives of these plugins. There's nothing preventing the community to develop a fully OSS Liveshare or Remote extension (and they are!)

Re: LazyVim

#365

Post by lemper »

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…

I've stopped using vim and started using visualstudio + vim plugin and called it a day. for me, it's just not worth it to tinker with truckload of plugins just to get ide features work.

Re: LazyVim

#366

Post by krab »

distcs wrote: post #248
eptcyka wrote: post #245

Earlier quoted context omitted.

What about control+c? Also, I've never used vim without remapping `jj` to .

Ctrl+C and Esc do not behave the same in all contexts. The correct replacement for Esc is Ctrl+[. What if you need to type `jj`? Not uncommon to do so while writing math or physics papers. a_{jj}

Not using this personally but there can be a timeout, or you do jkj. Fine if the letter sequence is rare enough.

Re: LazyVim

#367

Post by jcpst »

lagolinguini wrote: post #341
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…

> 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. Personally I've started paying for intellij and using it with it's vim emulation. I know it doesn't solve the p…

Intellij IDEs for my day job are awesome.

I do have a personal all-products license as well, but I hesitate to go “all in” and be dependent on them.

But it is ok to just use a lot of editors for different things. VS Code is ‘good enough’ a lot times. I like writing notes in emacs org-mode. NeoVim on the command line. Sometimes I use Helix, I think it hits a sweet spot between snappiness and minimal configuration.

Re: LazyVim

#368

Post by krab »

mgdlbp wrote: post #169
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…

> Canada ... out of fuel Referencing the Gimli glider. But does vim have any analogous issue? In matters of technical correctness FOSS is usually the more exacting. You won't find a 1 TB hard drive full at 931 GB of used space on Linux, for example.

What about reserved blocks in ext filesystem? With default settings, it will say 5 % free but writes will fail if you're not root.

Re: LazyVim

#369

Post by aerhardt »

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…

Completely agree, I've tried a full vim migration before and it's been a futile exercise. JetBrains with the vim plugin does it for me.

Re: LazyVim

#370

Post by danjac »

gsinclair wrote: post #342
Barrin92 wrote: post #147

Earlier quoted context omitted.

That's simply not the case because you will, very quickly, run into problems. One example I had with vim recently was that two different plugins both tried to format the same code and actually send each other into some sort of hell loop and crashed vim entirely because they called something in a circular fashion. That's absolutely representative of the kind of errors vim and neovim configurations have, because it's a…

You’re absolutely right that this can happen, but wrong that it is representative. Let’s take all the serious vim users in the world. How many have this kind of plugin hell experience? A tiny percentage. Serious vim users don’t try to create a kitchen sink IDE. They start with a vanilla base and with their way up, including just the features that are important to them. Starting with something like LazyVim is fine too…

I agree that vim is a perfectly fine text editor.

Yet half the (neo)vim people in this thread are yelling it's the One True IDE that can, in fact, do everything, and if you are using VSCode or IntelliJ or whatever then you must be a noob or too lazy to invest time in your tools.

Post reply on HN