Live data from Hacker News

Neovim v0.5

github.com

11–20 of 213 posts

Re: Neovim v0.5

#12
post #2

I'm excited for this release! Built in nvim-lsp, treesitter support, better support for accessing vim internals from lua are all awesome additions. I've been using the nightly releases for a while and it has been great! I'm looking forward to seeing the larger community now have access to the stable release! For people that are interested in knowing more, neovim is having a release stream on teej's twitch channel: tw…

What do folks these days use with vim-lsp to get an IDE-like experience? I’m wondering if it would be better than a coc/ccls setup.

Re: Neovim v0.5

#14
post #2

I'm excited for this release! Built in nvim-lsp, treesitter support, better support for accessing vim internals from lua are all awesome additions. I've been using the nightly releases for a while and it has been great! I'm looking forward to seeing the larger community now have access to the stable release! For people that are interested in knowing more, neovim is having a release stream on teej's twitch channel: tw…

What do folks these days use with vim-lsp to get an IDE-like experience? I’m wondering if it would be better than a coc/ccls setup.

I think the fact that it's built-in should not be overlooked.

Re: Neovim v0.5

#18
I've been using neovim since the initial fork. The Neovim 0.5 is by far the most impressive milestone yet. I tried it couple of months back (before release) and immediately jumped to support the developers through the Github Sponsors after trying it out.

https://github.com/sponsors/neovim

Re: Neovim v0.5

#19
Is anybody else uncomfortable about the idea that an LSP client is now baked into the editor (as opposed to being a plugin)? Are there big performance gains to this approach?

While LSP is great, it basically came from nowhere in the last couple of years. My concern: what if something definitively better comes along in another couple years, and we're "stuck" with this baked into the editor?

For context, using ALE, I've been able to gracefully migrate my language-specific helpers from pre-LSP to post-LSP universes, over the years as LSP helpers have become definitively better and faster, one language at a time, all without needing to recompile or download a new binary.

I'm very open to the idea that I'm missing something obvious, because I have a lot of respect for neovim and neovim contributors. I understand that neovim is not trying to replace vim but evolve it. This feels like a move away from plugins and into monolith territory, which feels like a big step. Curious to hear other's thoughts.

To be clear, I'm not for or against this, I'm mostly curious about the reasoning / thinking behind this, if anybody has links I'd love to read them.

Re: Neovim v0.5

#20
post #19

Is anybody else uncomfortable about the idea that an LSP client is now baked into the editor (as opposed to being a plugin)? Are there big performance gains to this approach? While LSP is great, it basically came from nowhere in the last couple of years. My concern: what if something definitively better comes along in another couple years, and we're "stuck" with this baked into the editor? For context, using ALE, I'v…

Presumably it's disablable. So if you want to use something else you can just turn it off and then use the plugin of your choice.
Post reply on HN