78
People that use Neovim really like Neovim | More than any other code editor, people using it want to keep using it | 2024 Stacked Overflow Developer Survey
(programming.dev)
Based on answers to the following question:
Which development environments did you use regularly over the past year, and which do you want to work with over the next year? Please check all that apply.
Neovim is the most admired code editor in the 2024 Stacked Overflow Developer Survey
Source: https://survey.stackoverflow.co/2024/technology#admired-and-desired-new-collab-tools-desire-admire
I must be a minority then. I tried it once - as in, I made a real, honest attempt at liking it and making it work for me - and all it managed to do is show me it's buggy and confused, and to convince me to steer well clear of it and stick to vanilla Vim.
I really really dislike Neovim.
Also, I question the vailidy of a survey in which VSCode is 13 times more "desired" - whatever that means, it's not like it's hard to procure - than VSCodium, given that VSCodium is VSCode sans the Microsoft spyware. Makes no sense to me...
I understand not liking the vim way of doing things (which seems not to be the case for you), but I've never heard anyone describe neovim as buggy. Not throwing shade, genuinely curious. What bugs did you encounter, and when was it?
Edit: I missed that you posted a link there. Interesting.
"Desired" and "Admired" are very strangle labels, it like the question(s) might have been:
In which case VSCodes high "desired" score just means that it was widely used?
I remember that post. I'm surprised that nobody has run into that problem until now. Did you open up an issue on the Neovim GitHub repository?
I ask because I don't see one and I want try to replicate the issue. I'll report it myself if I'm able to.
I don't care enough to bother, to be honest. Neovim, like Vim, is just a tool to me. It failed me, I moved on. I have more interesting things to spend my time on.
I care, because what you found is a bug. And I think it would be best to document the intended behavior and a temporary work around, and then fix the bug. So I'm doing just that.
I don't know how to open that post on my instance so I can reply to it, but if you're willing to give it another shot, I figured out how to get
indentexpr=to apply to all buffers from init.vim, using an auto command. Add this to your init.vim:I think I found a more direct way. I'm still looking into the details though.
You can get to the post using this link: https://threadiverse.link/lemmy.sdf.org/post/18253296
It's awesome that you were able to find a solution!
Thanks for this tip!
Ah, thanks for your efforts, you're very kind. But I'm done with Neovim. It's already wasted more of my time that it was ever going to be worth.
I wanted to try Neovim to give Treesitter a spin. In the end, I went with something much simpler that works immediately and without drama in Vim and does what I really wanted all along: simple, dumb autocompletion.
Can't use Pylance in VSCodium /rant
It's one of vscode's killer features (at least for Python), and I can't live without it (I tried).
Yes, I don't like it either; I wish I could use Pylance in Neovim or anything else LSP-enabled, but it is what it is.