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

291–300 of 537 posts

Re: LazyVim

#291

Post by majkinetor »

altonas wrote: post #271
majkinetor wrote: post #265

Earlier quoted context omitted.

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.

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 with your potential being maxed out at that point (if you are accepting anything less then most efficent workflow, given that time is the most precious resource).

Actually, when I look at how most of my colegues are slow using their tools of choice, even senior ones, I imagine I would rather kill myself then using such setup.

Re: LazyVim

#292

Post by geysersam »

oblio wrote: post #277
divbzero wrote: post #123

Earlier quoted context omitted.

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

[flagged]

As if there are "studies" backing the claim that arrow keys are easier to use for navigation than the home row keys...

Personally I don't want to move my hands from where I'm writing to the other side of they keyboard just to move the cursor.

Re: LazyVim

#293

Post by IceDane »

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

This reads so much like that macho programmer who wrote everything in assembler from a few decades ago. I will keep using Sublime Text. No need to suffer needlessly.

This is pretty ironic, given that Sublime Text is basically dead in terms of community, number of users, etc and definitely isn't a full IDE.

Re: LazyVim

#294

Post by baq »

stavros wrote: post #258
baq wrote: post #103

Earlier quoted context omitted.

> 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. I’ve done that a couple years ago after ~15 years of happy vimming. Still yearning for the text manipulation language combined with macros, but all the other gains significantly outweigh the worse editing capabilities.

What are the other gains you like?

There's an extension for almost everything, right there in the UI.

The fact that it's electron means there is native support for graphical preview in e.g. markdown, mermaid, plantuml, jupyter, etc.

Relatively sane defaults. I haven't tweaked much of the editor except the color scheme and shell startup timeout.

Zero messing around with language server setup. It's 'install extension' and go. Sometimes a window reload is required, but it restores the session intact, even with terminal history.

Remote ssh (and WSL on windows) is super seamless. The way I've used vim was always ssh+tmux. Most of this is unnecessary with remote ssh in vscode.

There's probably more but these are what comes to mind immediately.

Re: LazyVim

#295

Post by skydhash »

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.

One of the tips in The Pragmatic Programmer is "Achieve Editor Fluency", wherever it's Vim, VS Code, or Sublime Text. I use IDEA for java code because in my job, I browse code more often than I edit it, and IDEA is nice for that. I also use WebStorm for the JS part because it's also good for that. But I invested my time into VIM because I can do everything above with it and even more. I don't want my editor to become an IDE, I want it to be powerful in editing and allow for integration, as there are slews of tools that work with code and text.

You should invest in your tools, be it Vim or VS Code. I chose Vim and Sublime Text because of their speed, and JetBrains' IDEs because of their code analysis engine. You may have different criteria, but try to follow the tip.

Re: LazyVim

#296

Post by _7tgr »

oblio wrote: post #272
jahsome wrote: post #229

Earlier quoted context omitted.

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…

For what it's worth, the 'VSCode-level' functionality in my init.lua has probably required roughly a few hours of maintenance over the ~7 years I've been using Neovim. The LSP setup is just a matter of finding a plugin manager (or not), installing the lspconfig plugin, pasting in the config from the README, and inserting a single line that contains the name of the language server you want to configure.

It can definitely lead you down all sorts of twisty paths if you look at other people's elaborate configs and decide to do that sort of stuff yourself but it's very pleasant/low-maintenance if you stick to the basics (meaning roughly what people do with VSCode). It takes me roughly a few minutes to configure Neovim for a new language :)

(Of course, there's some other stuff in my init.lua that I've put there for fun, like clipboard and window management scripts, but that's not strictly necessary. I've spent a bit more time figuring out the Lua API to write these, but I personally think it's worth it for the extra ability to mold the editor to my needs).

Re: LazyVim

#297

Post by yodsanklai »

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.

on the other hand, using vim mode in vscode let you use vim where it shines: modal editing. It's the best of both worlds.

Re: LazyVim

#298

Post by skydhash »

oblio wrote: post #275
nextlevelwizard wrote: post #192

Earlier quoted context omitted.

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.

It's always been like this. Vim is an editor, and so is Sublime Text, Emacs, VS Code, Geany, Kate, Notepad++, and more. What sets vim apart is its ubiquity (it's been on every Linux box I touched) and its philosophy of editing text (modal editing). Apart from that, it's a matter of preferences and practicality.

Re: LazyVim

#299

Post by madsr »

_7tgr wrote: post #160
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'm playing into the joke here, but on most terminals, alt + will actually be sent to the program as + key. You can use this to avoid pressing escape in Neovim.

+1. I mainly use this approach. If your next intended move is to go to the next line, Alt-J will exit insert mode and go to the next line immediately. Also the same for Alt+w/W/b/B, Alt+o, Alt+0, etc etc and it's just a matter of using your left thumb at the same time as navigating.
Post reply on HN