Live data from Hacker News

Neovim 0.9

github.com

41–50 of 106 posts

Re: Neovim 0.9

#41
post #2

Congrats to the Neovim team! I know one complaint that people tend to have with nvim is that they can never get to a stable config that they don't need to keep tweaking; I used to be one of those users that kept making changes to their config but I've had a stable config for roughly 6 or so months now and I've been loving neovim and the fact that it's personalised exactly to my liking. So what I'm trying to say is th…

Any chance your config is public? I always find cool new stuff when I look at other people’s nvim configs

OP didn't reply, but here's my set of dot-files in case you still wanted to have a gander at someone's. You can find the Neovim configuration in the neovim directory.

https://github.com/AlexSWall/dot-files

Re: Neovim 0.9

#42
Since I've learnt vimscript and am relatively happy using it, what's the advantage of writing plugins in lua for neovim?

Re: Neovim 0.9

#43

I spent a good amount of time learning vim/neovim and installed tons of plugins, but in the end I didn't see the point. Language support is still nowhere near VSCode, let alone Jetbrains products. I do all my development on a macbook so ultra low memory or being installed by default is not a requirement. People praise vim/neovim for being small but to get any decent functionality you will end up with tons of plugins.…

> People praise vim/neovim for being small but to get any decent functionality you will end up with tons of plugins.

If a writer compares VSCode to Word and claims exporting as PDF is "decent functionality" making VSCode a useless tool does he even understand what he's looking at?

You have the same language servers as VSCode, GDB is integrated and works really well. On top of that you have the entire OS and unix philosophy at your fingertips. Even with vanilla vim I have many more features than I ever had with VSCode and the likes.

It's not all about buttons and pretty dropdrowns. I agree the discoverability could be better, but that's a necessary compromise for making just about anything you'd like to do possible.

Re: Neovim 0.9

#44
post #42

Since I've learnt vimscript and am relatively happy using it, what's the advantage of writing plugins in lua for neovim?

Better documentation and support. Since Lua is a well-established language, there's a larger community around it than something like vimscript. What I've heard from the community is that vimscript and its quirks are difficult to deal with, which complicates plugin development. Lua support means more complex and stable plugins, but if you prefer vimscript nobody's stopping you.

Re: Neovim 0.9

#45
post #39

I have tried many times to switch to Neovim, but I keep coming back to VS Code. 1. I can't create configs myself. 2. Astro, Lunar ... all break at sometime.

Agreed. Neither VS Code nor VS Codium (my preferred variant, telemetry-free) have ever broken my setup with an update, something I can’t say about NeoVim or Emacs.

Re: Neovim 0.9

#46
post #34

I spent a good amount of time learning vim/neovim and installed tons of plugins, but in the end I didn't see the point. Language support is still nowhere near VSCode, let alone Jetbrains products. I do all my development on a macbook so ultra low memory or being installed by default is not a requirement. People praise vim/neovim for being small but to get any decent functionality you will end up with tons of plugins.…

I prefer an editor that I can customize to my liking and I don't have a conflict of interest with the developers.

Same here. There's always struggle with software, so I prefer to struggle with the software, and not against it.

Re: Neovim 0.9

#47
post #14

Earlier quoted context omitted.

As a counterpoint of sorts, if you are accustomed to vim, moving to neovim entails almost zero switching friction. Everything works just like it's supposed to. In fact sometimes I get neovim instead of vim (when I run "vi" from the shell) and I don't even notice. I have a fairly simple vim config. I'm sure this means that I'm missing out on all the great new things about neovim, and maybe I'll get there some day. But…

> moving to neovim entails almost zero switching friction As a counter-counterpoint: I tried switching to neovim a couple of weeks ago, and gave up after half a day trying to get syntax highlighting working.

Strange considering neovim has syntax=on by default and it's not even needed in the config. What distro are you using?

Re: Neovim 0.9

#48
post #39

I have tried many times to switch to Neovim, but I keep coming back to VS Code. 1. I can't create configs myself. 2. Astro, Lunar ... all break at sometime.

I don't disagree, but then you shouldn't update Neovim if you are not ready for that. I'll go even farther: don't use Neovim if you are not going to write the config yourself.

Re: Neovim 0.9

#49
I've really tried to move from vim to neovim for a long time and spent many hours trying to configure it to behave like vim, but every time I try it breaks in unexpected ways or it hungs up, while vim for my workflow never flinks. I hope that they'll reach a 1.0 soon where things are more stable.

Re: Neovim 0.9

#50

I've really tried to move from vim to neovim for a long time and spent many hours trying to configure it to behave like vim, but every time I try it breaks in unexpected ways or it hungs up, while vim for my workflow never flinks. I hope that they'll reach a 1.0 soon where things are more stable.

I felt this way in the 0.7 and earlier days but since then it's been remarkably stable for me, at least.
Post reply on HN