Live data from Hacker News

Neovim 0.8 Released

github.com

181–190 of 230 posts

Re: Neovim 0.8 Released

#181

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

I know you asked for Neovim users, but as an Emacs user, I'll respond:

> If you use Neovim, can you share why you chose it over VS Code

Who said you can't use both? Neovim is a text editor, and VS Code is an IDE. There is overlap, but they serve different purposes.

I use Emacs because it has a lot of capabilities that make little sense in an IDE. I don't think many people use VS Code for reading email, for example.

And I use VS Code when it's more convenient than Emacs (e.g. debugging).

Re: Neovim 0.8 Released

#182

Earlier quoted context omitted.

Average joe-schmoe Neovim user here. My goal is not to emulate VS Code and other similar software. I enjoy Neovim for programming mainly because... - First and foremost, I love the text editing features Vim has (eg. the movements, modes, keys etc). It just feels great on my hands. - It's minimal. Well, you are free to make it as minimal or as bloated as you would like to ;) - For me, it sort of gamifies text editing.…

Agree that it gamifies text editing – vim motions are fun, even though I largely don't miss them in VS Code, or I use a vim extension when I do. > …myself and a lot of other Neovim users are basically masochists to some extent. It's great of you to say this, and heartwarming to see a sense of self-awareness on HN. It's easy to rationalise our tech choices away (vim = speed, efficiency, freedom!). It's harder to admit…

[deleted]

Re: Neovim 0.8 Released

#183
post #82

Must every neovim release thread be brigaded by naysayers asking the same question for the 1000000th time? If you don't like its value proposition, don't use it. Simple. Keep using your IDE or whatever solution you prefer. This is almost exclusively happens in (neo)vim threads, and its so utterly distracting. That there is an entire community camped around neovim should answer your question about why anyone choses it…

But then what would we talk about? The update?

Re: Neovim 0.8 Released

#184

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

when i switched to neovim, vim did not have :terminal and that was the real killer feature to me. neovim also had better async communication support than vim did. vim caught up, but in the meantime i had already gone full on nvim. Now, with the lua support, there's no way to make my config compatible between the two, and i'm "stuck" on nvim.

Re: Neovim 0.8 Released

#185
post #21

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

I switched to neovim because of LSP (Language server protocol) support. I know there are libraries (or whatever cool kids call it these days), which brings this functionality to og vim, but the lsp integration in neovim just works so nicely out of the box.

og vim does not have full lsp out of the box. However it does have the the api and options to implement one easily.

see: https://vimhelp.org/channel.txt.html#language-server-protoco... https://vimhelp.org/channel.txt.html#channel-mode

Re: Neovim 0.8 Released

#186
post #106

Earlier quoted context omitted.

> If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? VS Code is a proprietary, spyware-riddled, resource-wasting worked example of why "modern" software sucks. Also for my personal use, everything that's not vim suffers from being not vim; it would cost me effort to switch for no cl…

> VS Code is a proprietary, spyware-riddled, resource-wasting worked example of why "modern" software sucks. Perspectives like these (and others in the thread) remind me that there exists a separate cohort of engineers from people like myself which have absolutely polar opposite views. I respect your opinions, though I couldn't disagree more with them! :) Well, except the bit about VSCode having "spyware". That's not…

Vscodium is pretty great though.

Re: Neovim 0.8 Released

#187

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

when i switched to neovim, vim did not have :terminal and that was the real killer feature to me. neovim also had better async communication support than vim did. vim caught up, but in the meantime i had already gone full on nvim. Now, with the lua support, there's no way to make my config compatible between the two, and i'm "stuck" on nvim.

Embrace, extend, extinguish!

Re: Neovim 0.8 Released

#188
post #149
post #120

Earlier quoted context omitted.

No. Microsoft's general reputation for spying on its users renders "spyware" a reasonable shorthand for what it either does now, or perhaps is reasonably likely to do at some time in the future. I would fall back to the softer "telemetry" ONLY IF they were to provide some sort of genuinely reliable affirmation that it's not spying, which I don't think they could do today absent legal or other generally obvious incent…

I mean, you can say whatever you want - you only diminish your own argument by doing so. It's like the boy who cried wolf - if you keep shouting "spyware" with no true evidence of spyware, then by the time that "spyware" actually is happening, no one is going to care. > what it either does now Spyware is defined (Google) as "a form of malware that hides on your device, monitors your activity, and steals sensitive inf…

Calling spyware an "imagined hypothetical" re Microsoft is like calling "too hot coffee" an "imagined hypothetical" for McDonalds.

They've already done it a bunch. Are you naive enough to 100% believe their pinky swears?

Re: Neovim 0.8 Released

#189

A text editor without a well rounded GUI story isn't worth it for me. There are all these desperate projects each with their own focus, ranging from "simple graphics acceleration" to "tons of bells and whistles, animations and ad-hoc UI extensions". UI should be thought out at PRs and issues, but the same people who develop the main core. But they don't have to, because they're making a terminal application, which ha…

> A text editor without a well rounded GUI story isn't worth it for me.

ed is the standard text editor.

https://www.gnu.org/fun/jokes/ed-msg.html

Re: Neovim 0.8 Released

#190

Earlier quoted context omitted.

I was not familiar with Helix or Zed, so I took a look at the links. Both webpages prominently state that the editors are written in Rust. This reduces my interest in both projects. As a user, I do not care what language my editor is implemented in. Maybe I want a fast editor, or maybe I want a feature-rich editor. The closest I would come to caring about this is if I want an extensible editor - can I extend these ed…

I don't get along very well with the HN Rust Community (and I think I'm even less popular with them than they are with me), but fair is fair and the Rust folks have been absolutely revolutionizing the modern terminal experience. Put differently, I take the opposite view: seeing that a piece of terminal kit is written in Rust gives me a quite high Bayesian prior on the quality and usefulness of the tool. Something lik…

> seeing that a piece of terminal kit is written in Rust gives me a quite high Bayesian prior on the quality and usefulness of the tool.

I maintain clap, the most common CLI parser for Rust. When soliciting feedback on changing some of the `--help` formatting, a piece of a feedback I got from a couple of people was some of the distinctive look told the reader it was written in Rust and using clap and "that means a certain baseline of quality and behaviour".

Post reply on HN