6 ms·

Aren't most people using neovim now?

by gaving 10y ago

seletskiy 10y ago
No, not at all. neovim is still lacks stability.
- hkmix 10y ago
  Is this from experience? I've switched back to regular vim from neovim because of platform support, but I've never had stability issues when I did use neovim.
  - seletskiy 10y ago
    Yes, it's from experience. I'm maintainer of https://github.com/SirVer/ultisnips https://github.com/SirVer/ultisnips snippet plugin for vim, and I'm often see issues when people can't get it work under nvim due nvim internal issues.
- erelde 10y ago
  From experience: neovim often forgets basic settings for indentation, it's the only flaw I've experienced myself but it's enough that I can't use it.
lojack 10y ago
I personally use nvim, but most of my coworkers (also vim users) haven't yet switched. There's a surprising number of people that are aware of nvim but haven't bothered switching because vim works fine for them.
executesorder66 10y ago
The main selling point for neovim when I found out about it was the async plugin support. And I remember reading that the creator of neovim mainly did it because the maintainers of vim refused to accept his patch to add async plugin support for vim. But about a month ago, vim added async plugin support. So now what? I switched to neovim, and now I am undecided if I should switch back to vim or not. neovim has a fresh start, cleaner code base but less support/timetested code than vim. What do you guys think?
- sdegutis 10y ago
  My understanding was that Neovim's main strength was the fact that it is a fresh rewrite for modern platforms only. Whereas Vim has tons of legacy code in it for all sorts of legacy platforms, which makes it harder for people to contribute code, and makes it harder for the dev team to find and fix bugs, or to add features, etc.
  - seren 10y ago
    In any case, whatever the outcome of the fork is, this is an interesting experiment : Will the cleaner code base, using more extensively tests and CI move faster than the legacy one ? Not accounting the number of people contributing to each project, the logic said it should. It will be interesting to see how long it takes to pay the dividend.
nilkn 10y ago
Not that I know of. I mean, I've been a heavy vim user for years and haven't even bothered trying neovim.

Aren't most people using neovim now?

by gaving 10y ago

Aren't most people using neovim now?

seletskiy 10y ago

No, not at all. neovim is still lacks stability.

hkmix 10y ago
Is this from experience? I've switched back to regular vim from neovim because of platform support, but I've never had stability issues when I did use neovim.
- seletskiy 10y ago
  Yes, it's from experience. I'm maintainer of https://github.com/SirVer/ultisnips https://github.com/SirVer/ultisnips snippet plugin for vim, and I'm often see issues when people can't get it work under nvim due nvim internal issues.
erelde 10y ago
From experience: neovim often forgets basic settings for indentation, it's the only flaw I've experienced myself but it's enough that I can't use it.

lojack 10y ago

I personally use nvim, but most of my coworkers (also vim users) haven't yet switched. There's a surprising number of people that are aware of nvim but haven't bothered switching because vim works fine for them.

executesorder66 10y ago

The main selling point for neovim when I found out about it was the async plugin support. And I remember reading that the creator of neovim mainly did it because the maintainers of vim refused to accept his patch to add async plugin support for vim. But about a month ago, vim added async plugin support. So now what? I switched to neovim, and now I am undecided if I should switch back to vim or not. neovim has a fresh start, cleaner code base but less support/timetested code than vim. What do you guys think?

sdegutis 10y ago
My understanding was that Neovim's main strength was the fact that it is a fresh rewrite for modern platforms only. Whereas Vim has tons of legacy code in it for all sorts of legacy platforms, which makes it harder for people to contribute code, and makes it harder for the dev team to find and fix bugs, or to add features, etc.
- seren 10y ago
  In any case, whatever the outcome of the fork is, this is an interesting experiment : Will the cleaner code base, using more extensively tests and CI move faster than the legacy one ? Not accounting the number of people contributing to each project, the logic said it should. It will be interesting to see how long it takes to pay the dividend.

nilkn 10y ago

Not that I know of. I mean, I've been a heavy vim user for years and haven't even bothered trying neovim.