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

511–520 of 537 posts

Re: LazyVim

#511

Post by stnmtn »

lvass wrote: post #448
majkinetor wrote: post #188

Earlier quoted context omitted.

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…

>just login in GitHubs vscode Imagine if you had to do that to every program you want to configure. Sure, rsync/git cloning your config may be less straightforward than logging in somewhere, but it's far more convenient when you have to configure dozens of programs anyway.

I understand your point, but the person above has to login to Git every time they want to pull down their .vim config. It's a similar thing.

Re: LazyVim

#512

Post by stnmtn »

Arch-TK wrote: post #437
danjac wrote: post #350

Earlier quoted context omitted.

> Again, I would like to stress, I am not trying to make any objective claims as to how correct your approach is. I am simply observing that there seem to be broadly two categories of programmers. Those who feel like investing time in learning and writing/modifying "tooling" is worthwhile and those who do not. I feel like you fall into the latter category. I use zsh, with customizations. I know git, and mercurial, an…

Okay, so it seems you certainly fall into the category of people who generally find it worthwhile to learn and configure/modify tools. So I really don't understand how you came to the conclusion that neovim and vim are not worth the time. Neovim takes a lot less time (weeks to months) to learn than something like git (months to years), while I know both very well, I find that I am more often interacting with my text…

> how do you justify the friction of VSCode (as you yourself put it, VSCode isn't perfect) when you have tools such as vim, neovim, emacs, or whatever else that are designed to help reduce friction for a modest but steep initial learning curve.

Because VSCode also is designed to reduce friction for a modest but (less) steep initial learning curve.

I have used vim a lot. I've also used VSCode a lot. It sounds like you haven't dived into VSCode in the same way you've dived into Vim. I'm trusting you that your Vim setup, after tweaking it to your liking and diving into it, is perfect for you. So I'm asking you to trust me (and the other commenter), and my VSCode setup, after tweaking it and diving into it, is perfect for me.

Using Vim emulation in VSCode, plus the richness of VSCode configurability, I have an environment I'm over the moon about, and it was less steep of a learning curve than Vim.

You seem to think that anything that isn't Vim or Emacs can not compare. I'm asking you to reconsider that.

Re: LazyVim

#513

Post by stnmtn »

CiTyBear wrote: post #427
_mis1 wrote: post #412

Earlier quoted context omitted.

> Everytime I test vscode, it does not do what I want and when I look into it, I can't configure it correctly. Vim has always my back. Can you expand on this? What specifically does not work for you on vscode?

I don't believe in 10x programmer and know this term only from HN. I live in France and after 10years programming, I never heard a collegue said "I am a 10x programmer". However, I always make sure any git project can be worked on with any IDE. I use vim, some use PyCharm and most of them use VScode and it works fine. However, I can tell you my main pain point in using VS code vs vim: project switching. Many times I…

This exists in VSCode, it's called workspaces. You save a .workspace file, then with either an extension like this one[1] bound a key (very easy to do), or just using the command pallette to open it, you can switch to any workspace you want; in the same window or a new window, and you can have the exact files/layout/tabs you had open the last time you were using that workspace open automatically.

It's very simple. It's certainly more simple from first principles than your method, but if you are adept at using the shell as you clearly are, then your 'fg && vim ctrl-p` certainly must feel pretty natural; but I hope you understand that this is only because you have probably lived on the shell for many years. I used to do that too, with tmux and vim configs, but now I find it much simpler, faster, and better to use VSCode. I'm not saying you should switch, I'm only saying that just because it's not on the shell doesn't mean it's worse.

[1] https://marketplace.visualstudio.com/items?itemName=sadesyll...

Re: LazyVim

#514

Post by tenacious_tuna »

lawn wrote: post #212
majkinetor wrote: post #188

Earlier quoted context omitted.

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…

For me it feels easy to migrate my config. Just copy/clone the dotfiles, launch neovim and run a command to update the plugins and everything is good to go.

> Just copy/clone the dotfiles, launch neovim and run a command to update the plugins and everything is good to go.

The last time I did anything like this was back in 2016, where I'd cribbed a relatively customized vim config that my boss had rigged up for python and C++ development. I spent so much time troubleshooting plugins and integrations across the various systems I was trying to do development on, I've been burned out on "just install a plugin and update stuff."

Even now, working with Ruby and VS Code, I feel like I have to troubleshoot my plugin stack once every other month because some behavior isn't working quite right. I loathe the idea of ever having to set this up on another machine, and I miss when I was a Mac developer who just (had to) use XCode. It was flawed, certainly, but the base function set Just Worked.

I used to have the stomach for having to chase down config issues and customizing my esoteric editor, but now I get extremely suspicious whenever someone says something like "just copy the files and re-run the install command". It's never been that simple in my experience.

Re: LazyVim

#515

Post by xigoi »

danjac wrote: post #177
erfgh wrote: post #153

Earlier quoted context omitted.

One of the basic tenets of Vim is that it is not an IDE. It is a text editor. By the way, if you need an IDE for Python then you're missing the point of Python.

I don't need an IDE for Python. Of course I can use a plain text editor if I want. Hell, nano even. But right now, today, at work, I have a large legacy Django project to maintain, and it's kind of nice having little things like auto code formatting and linting to help me as I go and prevent me from making dumb mistakes and saving me a ton of time so I can focus on the problem at hand, not making the code look nice f…

You can very easily set up (Neo)Vim to run Black on save.

Re: LazyVim

#516

Post by Arch-TK »

stnmtn wrote: post #512
Arch-TK wrote: post #437

Earlier quoted context omitted.

Okay, so it seems you certainly fall into the category of people who generally find it worthwhile to learn and configure/modify tools. So I really don't understand how you came to the conclusion that neovim and vim are not worth the time. Neovim takes a lot less time (weeks to months) to learn than something like git (months to years), while I know both very well, I find that I am more often interacting with my text…

> how do you justify the friction of VSCode (as you yourself put it, VSCode isn't perfect) when you have tools such as vim, neovim, emacs, or whatever else that are designed to help reduce friction for a modest but steep initial learning curve. Because VSCode also is designed to reduce friction for a modest but (less) steep initial learning curve. I have used vim a lot. I've also used VSCode a lot. It sounds like you…

>You seem to think that anything that isn't Vim or Emacs can not compare. I'm asking you to reconsider that.

I don't think you have read the discussion between me and the other commenter very thoroughly if you came to this conclusion.

I have repeatedly re-iterated my stance so I would rather not do it again but tools such as VS code are inherently inflexible (I have put a couple of weeks into trialling and configuring vscode) for good reasons and to tailor to a specific audience.

My argument is that for the other audience, tools such as Vim or Emacs (or in some extremes, writing your own editor or using something even more obscure) offer superior flexibility and offer the possibility of much reduced friction in exchange for more time needed to learn, configure and maitain and that this setup is worth it for that different target audience which the person I was talking to has indicated membership in.

For a more in depth overview of my stance, please don't skim read what I wrote and as a result jump to incorrect conclusions.

Re: LazyVim

#517

Post by eptcyka »

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.

Having fiddled with file descriptors, I could never live with such a remap. To each their own :)

Re: LazyVim

#518

Post by Draiken »

airlust wrote: post #498
Draiken wrote: post #450

Earlier quoted context omitted.

> that macho programmer Why do people keep making value judgements about people that built tools they trust like they should be ashamed or something like that? Parent simply explained his process and why he uses vim like that and why he doesn't like VSCode. There's nothing there that says "macho" in any shape or form. I don't understand this need to put labels on others like this. Maybe it makes people feel better ab…

I think it’s because of the statement “you can only copy what you understand”. I get the sentiment, but comes off as paternal rather than collaborative.

Could be, but how is that macho in any way?

If anything, it's sound advice. Most of my early day colleagues copy/pasted everything from StackOverflow without understanding any of it, causing huge issues down the line.

They were the classic duct-tape programmers and that didn't help them at all to grow as programmers and even impacted their careers.

Labeling this as "macho" implies that properly understanding your tools is actively bad. Couldn't be further from the truth.

Re: LazyVim

#519

Post by VectorLock »

xyzzy_plugh wrote: post #46
VectorLock wrote: post #37

Earlier quoted context omitted.

But it has to use your code for inferencing, doesn't it? So it is sending it to someone. I see this being a blocker at a lot of places. I know in my workplace the infosec people are apoplectic about it and we supposedly have a 'partnership' with OpenAI.

You're not wrong, and I realize there is nuance here, but if you're using GitHub you are already sending your code to Microsoft.

I don't think using GitHub is a prerequisite for using Copilot but I could be wrong.

Re: LazyVim

#520

Post by strokirk »

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.

Just because it’s predefined doesn’t mean it’s suboptimal. On the contrary - anything I do myself likely has less about of thought and consideration from an officially published configuration.
Post reply on HN