Live data from Hacker News

LazyVim

lazyvim.org

181–190 of 537 posts

Re: LazyVim

#181
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…

Same sentiment here. After 2 decades of development and having been through phases such as Gentoo, Vim+plugins, and other deep dive hobbies, I enjoyed the time spent, but now I just want something that works out of the box. I've found IntelliJ/GoLand with Vim bindings to work well for me. That Vim muscle memory is something I'll never get over.

Re: LazyVim

#182
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…

You can have it both ways! Use neovim to handle key presses in VSCode, keep all the benefits of a text editor that (mostly) Just Works.

- https://github.com/vscode-neovim/vscode-neovim

Re: LazyVim

#183
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…

> 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 me exactly what I want. That's because the environment it creates has been fine-tuned based on feedback from thousands of users with similar requirements to my own. There's no need for me to modify anything, any more than I modify my car or my trousers. It's simply ready for me to do professional work, and whenever I have special requirements, I know that I will find an extension that caters to them also. I don't need or want to reinvent a wheel that has been invented hundreds of times already, and polished to perfection through more man-hours than I could ever hope to invest myself.

Re: LazyVim

#184

A bit off-topic, but I wonder how much Copilot/GPT cuts into the market share of editors like vim and emacs. I used emacs for the past few years, but I recently switched (back) to vscode because the Copilot integration is really good. There are a lot GPT integraton packages for other editors, but they don't come close to the deeper integration that vscode has. And of course, vscode will probably get priority treatmen…

Copilot has native NeoVim support

I don't know what kind of GPT you want in your editor. A colleague of mine attached the llama model to his vim, but that doesn't seem too useful to me.

Re: LazyVim

#185
post #146
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 cant stand VSCode anymore after using Zed[1]. I mean it was always clunky but there weren't better options. Now there is. 1: https://zed.dev Edit: I did use Helix for awhile (long enough to still have muscle memory for their editing model) but it’s just not there yet and eventually moved on to Zed.

The description looks cool. It's macos only though for now.

Re: LazyVim

#186
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…

If you want IDE like features, then of course an IDE is a better choice. I've never understood why people and to extend vim to try to make it half of an IDE.

a colleague of mine answered the same question with: "jetbrains products reek of java"

which i translated to "cluttered ui" and "not responsive".

Re: LazyVim

#187
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 really think this is the best way to use it for many people. You need something more complex? It's ok to bundle vim with any of great IDE's out there.

I learned how to change colorscheme more than 20 years ago because my CRT monitor made it impossible to read comments on default themes. I use same command today on my local terminals, bastions accessible via web or remote sessions ... for basically the same reason.

If you code from one machine spending time to set up IDE and then leaving it be makes sense. But if you are more of an admin, or learn a lot and jump from host to host, from learning platform temporary environments to cloud environments, from mobile to some remote mainframe that is being decommissioned for past 7 years? You could just figure out how to change 2-3 basic options and have a predictable environment for next few decades.

Re: LazyVim

#188

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 vscode with config, hotkeys, extensions and whatnot, the same as on the desktop.

I do miss vim editing constantly, and I could never feel vim emulations as a native thing, but vscode is really awesome, particularly its keyboard centric design and sync.

Once vim has this "works everywhere and my setup installs in 1 command" I will get back to it.

Re: LazyVim

#189

What was the name of the original Vim magic-auto-default setup project? I wish I could remember it! There used to be so many Vim questions on Stackoverflow from people who installed Vim ________ (?) and had no idea what it did. The advice was always: "Stop using that, and learn Vim." This project smells like that. There are two types of Vim users: 1. "Stop trying to make Vim and IDE with all your fancy plugins, learn…

>You have to learn Vim's terrible, verbose, antiquated commands in depth in order to justify using Vim. If you don't use q: (q colon) and q/ (q forward slash) in Vim, for example, you probably don't know Vim well enough to justify the efficiency loss you have compared to you using a modern IDE with multiple cursors.

How is scrolling through your past commands and searches anything like having multiple cursors?

If I want to use the same command I just type `:` followed by the start of the command and press up and it automatically fills in the rest of that command and I can even go back and forward in that history. Same with searching.

Also how is any of this "efficiency loss". Whenever someone talks about efficiency loss or performance in their IDE it is usually some very niche thing that they have gotten good at, but often the house of cards crumbles when they try to do anything else.

Re: LazyVim

#190
I'm Ruby developer, and tried multiple times to switch to vscode or one of these heavy IDE like plugins. All the time I'm back to my simple setup which is basically vim + fzf(powered by ripgrep). CTRL+P I run fzf to find files, CTRL+F to scan files content. It's so fast, that every time I'm doing the test switch to another tool, I'm missing this speed and get back to it. Some time ago I wrote an article for company that I used to work for, describing my workflow: https://thecodest.co/blog/rails-development-with-tmux-vim-fz... you can check it for more details.
Post reply on HN