Live data from Hacker News

LazyVim

lazyvim.org

281–290 of 537 posts

Re: LazyVim

#281
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 can identify with much of this. After an unfortunate bout of Java development, I was flung into the arms of Intellij, steadily won over by the indexing and the reliability of the refactoring tools. The Vim plugin was good enough and defining some chords for editor shortcuts resulted in a kind of fucked up fat vim emacs mode that was quite productive. I, too, got fed up of spending inordinate amounts of debugging vi…

I somewhat like Intellij too, but it seems insanely slow, esp. with the Vim plugin. I have to slow down my editing sometimes, because all it's fancy features can't handle the speed.

Re: LazyVim

#282
post #217

Earlier quoted context omitted.

You get exactly the same functionality with (neo)vim plugins. Only difference is that because vim has been open-source for decade, there are many many more plugins, and hence the choice is harder to make. VSCode also helped improve the (neo)vim experience (e.g. language servers) Comparing VSCode and Vim is like comparing a standard calculator with an RPN one.

> 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,…

FWIW, I just needed to install the default nvim-lspconfig plugin (it's provided by the Neovim maintainers, and it doesn't do anything besides provide default LSP server configs for a lot of languages to the builtin Neovim LSP client), paste in the keybinds recommended by the README, and call lspconfig.rust_analyzer.setup in init.lua. Configures itself to start whenever rust_analyzer is in PATH. Seems to work well enough! I don't think it's missing any functionality.

Re: LazyVim

#283
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 think your experience report of the NeoVim subreddit is severely misrepresentative of reality. I have never seen a RTFM response. Many answers point to exactly which part of the documentation would be helpful. Your Jenga tower of dependencies is much more imagination than fact. If you want Black to format your Python files on save, write an autocommand. That's what they're there for. If you need help to do that, as…

> If you want Black to format your Python files on save, write an autocommand. That's what they're there for. If you need help to do that, ask for it.

The real question would be:

Why does the 50 year old editor with supposedly a huge community and tons of editors not have support for a popular formatter for probably the most popular programming language on the planet, and instead everyone has to write their own (probably buggy) variation of that integration?

Re: LazyVim

#284
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.

I've personally been test driving JetBrains Fleet and have to say that it's pretty okay for most of my lightweight dev needs: https://www.jetbrains.com/fleet/

It's still a bit early for it and it doesn't have the same ecosystem that VSC has, but it'll probably be even better in 1-5 years and is decent already.

For most of the more heavy work I just use JetBrains IDEs, but that's very clearly a no go for the less capable devices like my netbook.

For even lighter options, on Windows there is Notepad++, which has been okay although not an IDE.

There's also CudaText, which feels quirky but has decent language support: https://cudatext.github.io/

Maybe even something like Geany is worth a look, depending on your needs: https://www.geany.org/

Re: LazyVim

#285
post #248

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}

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.

Re: LazyVim

#286

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.

Re: LazyVim

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

You're not the only one, but my configuration is the opposite of yours.

These are the three lines I always use on any vim install.

    let loaded_matchparen = 1

    syntax off

    map ; :
The first two lines are crucial, because I find rainbow colored text and flashing punctuation extremely distracting. If you find monochrome code unreadable, then that's a problem with your formatting style that you can easily fix.

The last line is really handy for not having to hold down shift so much.

Re: LazyVim

#288

Earlier quoted context omitted.

Setting up vim with IDE features takes an hour maximum + 2 minutes per additional language. If that is too much for you, you could have used any of the various vim/nvim distributions with the features already there. You could have even used Doom Emacs with vim keys . If you don't want to use vim, I do not mind whatsoever, but if you put in a bit of effort the solution to your problems would appear.

Sure, it's one hour if you did that already 20 times and you know the ecosystem. An hour is barely enough to go through the vimtutor which itself is pretty basic (aka you won't get far with it, so you need to keep learning and practicing). If you are a vim newbie, it takes a lot of time to figure out you need plugins, then figure out how to install plugins, then what's the difference between plugin installers, findin…

> If you are a vim newbie, it takes a lot of time to figure out...

The horror!

Re: LazyVim

#289
post #277

Earlier quoted context omitted.

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

[flagged]

the bindings are by far the best thing about Vim

Re: LazyVim

#290
post #193
post #169

Earlier quoted context omitted.

> 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.

This was supposed to parody how some of Vim's default shortcuts just flat out do not work on non-US keyboards, because e.g. typing [ requires pressing AltGr+8 on German layouts, but Ctrl+AltGr+8 is not the same thing as Ctrl+[. And yes, it was also a reference to the Gimli glider.

us international with dead keys is superior
Post reply on HN