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

271–280 of 537 posts

Re: LazyVim

#271

Post by altonas »

majkinetor wrote: post #265
altonas wrote: post #254

Earlier quoted context omitted.

That's the thing, I absolutely don't want to do a bunch of tiny tweaks. I want to write (react) code. For me personally I feel like tweaking an IDE gets in the way of that. Yet I can take a clean install of lazyvim, use mason to install the react language server, and install copilot, and then I can immediately start working. And so that's what I actually do, and I find that to be much more pleasant (and lightweight)…

Then you musta accept suboptimal UX. Its one way to live your life.

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.

Re: LazyVim

#272

Post by oblio »

jahsome wrote: post #229
p-e-w wrote: post #217

Earlier quoted context omitted.

> Only difference is that because vim has been open-source for decade, there are many many more plugins No, the main difference is in the quality of plugins, not in how many there are. For example, Rust-Analyzer provides an official VSCode extension, which is professionally maintained by members of the Rust core team. The extension is part of the Rust-Analyzer project itself, and can be installed with a single click,…

I'm a vim user, but only because of the keybinds. I use VS code an equal amount because I often get too frustrated trying to wire the disparate vim tools. The never ending fiddling and 30-step process to get the equivalent of one click in vs code is exhausting. The people who _enjoy_ the toil seem to truly struggle to comprehend that someone might not want to spend hours upon hours learning how to get things working,…

> The people who _enjoy_ the toil seem to truly struggle to comprehend that someone might not want to spend hours upon hours learning how to get things working, only to immediately forget.

It's worse than that, it's a religion. Many of them truly seem to believe they're achieving a higher "hacker rank" or something, while most of it is just tedium and very low level learning.

It's rarely learning huge, game changing concepts. Frequently it's just chasing obscure docs to obscure forums to obscure repos for stuff some PhD student half baked a decade ago on their way to their biochemistry thesis.

Guess what, I work in DevOps, that's just my dayjob, anyway, I don't want to do it as a hobby in Vim, too :-))

And I say this as an "also Vim user". I.e. I use Vim and I've used it for more than a decade, just not exclusively, best tool for the job and all that.

Re: LazyVim

#273

Post by palata »

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

Earlier quoted context omitted.

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…

> The chainsaw with ready made attachments is way easier to get going, but in return you have to carry the chainsaw with you and if there are any problems with the tool itself you probably aren't going to be able to fix or modify it yourself. This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. When I write Python code, the Python extension gives…

> This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for.

Then just use the chainsaw... and accept that the knife may be absolutely perfect for the tasks of somebody else.

Re: LazyVim

#274

Post by rajamaka »

danjac wrote: post #150
dcow wrote: post #144

Earlier quoted context omitted.

This is why I strictly adhere to vanilla Vim.

I use vanilla vim when I have to ssh into a server and work on some config files. As such, I much prefer it to nano, and it's installed, or easily installable, on any Linux server. For that use case, it's absolutely great. No complaints.

I spent years and years enjoying using vim for the same purpose when I was a sysadmin. I was absolutely disgusted beyond belief to find out people actually used it as their daily IDE when I became a developer.

Re: LazyVim

#275

Post by oblio »

nextlevelwizard wrote: post #192
p-e-w wrote: post #183

Earlier quoted context omitted.

> The chainsaw with ready made attachments is way easier to get going, but in return you have to carry the chainsaw with you and if there are any problems with the tool itself you probably aren't going to be able to fix or modify it yourself. This is where your analogy breaks down for me. The "chainsaw" (VSCode) is absolutely perfect for the tasks I'm using it for. When I write Python code, the Python extension gives…

It does not break down. Chainsaw is very good at doing chainsaw things. If what you need to do is cut down bunch of trees then chainsaw is exactly what you need. No one in their right minds would start with a knife and start building it into a saw and then attach a motor to motorize it. Mind you we were carving a bowl, but as per Internet argument you completely dismissed the use case and inserted your own. If VSCode…

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.

Re: LazyVim

#276

Post by conaclos »

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

The last version [0] of nvChad uses also lazy.nvim under the hood. I am not sure how this could help in your case.

[0] https://github.com/NvChad/NvChad/releases/tag/v2.0

Re: LazyVim

#277

Post by oblio »

divbzero wrote: post #123
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…

Was that expressly written to parody Vim? If so, this line is particularly spot on: > 'left' actually means right

[flagged]

Re: LazyVim

#278

Post by mvanbaak »

dmi wrote: post #240
p-e-w wrote: post #148

Earlier quoted context omitted.

> Was that expressly written to parody Vim? Yes. The advice to turn the yoke upside down is supposed to reference remapping Caps Lock to Escape, without which Vim destroys your pinky on a standard keyboard. But it's the choice of professionals, so what can we do?

I've been using Ctrl-[ instead of Esc for so long that I forget that a lot of people don't know about it. This may not be convenient on non-English keyboard layouts. More alternatives: https://vim.fandom.com/wiki/Avoid_the_escape_key

small fun fact: I switched to this when the escape key was taken from me (thanks again NOT apple) After switching to a newer MacBook that has the escape key I did not start using that again, but stuck to the Ctrl-[ as it just works.

Re: LazyVim

#279

Post by lawn »

joshka wrote: post #108

I dallied in this briefly, but couldn't get a good rust setup exactly how I liked, so went back to vscode pretty quick. Perhaps there's a good lazy+rust guide somewhere? I ran into the usual sorts of problems of some random plugin with instructions for how to install it in some other plugin manager for nvim, which means you have to learn two plugin managers and both their underlying concepts in order to port the conf…

You only need one plugin manager.

Most plugins only contain examples for some of them, but in the general case you can just add the GitHub url to the manager and you're good to go.

Re: LazyVim

#280

Post by thiht »

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 like being sucked back into the Microsoft ecosystem

You’re not though, there’s no lock-in.

Post reply on HN