Hacker News new | past | comments | ask | show | jobs | submit login

I have been using neovim for months now with no issues I can attribute to neovim. The terminal mode can be useful, although I still prefer my current tmux setup. I have been using it with linux and osx, building from source.

I suspect most users could download neovim, symlink their .vimrc/.nvimrc, alias vim=nvim and not be able to tell the difference.




As a note, one does not symlink to `~/.nvimrc` anymore. Things are now in `~/.config/nvim/` with the rcfile in the `~/.config/nvim/init.vim`. This was a bit of a surprise for me the other day when my `nvim` instance failed to pick up my settings and refused to identify a `backupdir`.


If that's the case why use it? I'm still holding out for Neovim's killer feature; I'm not switching just because they use more modern APIs or removed Amiga support; I don't care about those things as an end user.


Proper async plugins are the killer feature. For example, if you're using neovim then Syntastic doesn't block the UI when it runs checks. Also off the top of my head, built in terminal emulator and 24 bit color support and far easier integration with external programs. Eventually my hope is that we will have real vi-mode plugins for IDEs that actually load up (neo)vim, though those sort of things are still in their infancy.

I'm a very heavy vim user and have been using neovim for a while now. It causes me zero issues even following git master, but I can definitely notice improvements.


> Proper async plugins are the killer feature.

I hope there's more that than. I personally don't use any plugins for which this is a problem. Not doubting those plugins exist, but apparently you can get by as a Vim user without them.

I see potential for the embedding api. If I could run Vim on a server and connect to it from a web app I would find that to be very compelling. Maybe there are other features that will set it over the top, but I'm still waiting.


If you're using vanilla vim I don't think there's a whole lot neovim will offer you at present. I think there will eventually be some performance improvements in the core areas, but they haven't really started on that yet.

Async support is a big deal for a lot of people though (and it's neovims original raison d'etre). For example, not having :make (well, :Neomake) block on compile is pretty significant by itself. Under the hood getting real async tasks required/requires a ton of rewriting because of how Vim was architected. Those changes were made deliberately and weren't just so that they could use all these fancy new libraries.

So I guess I'd liken it to Windows when it went from the 98 days to WinNT/2000 - keeping things working about the same while laying the foundation for bigger improvements later.

On the other hand, I don't see much downside to moving to neovim either. It is interchangeable (in my experience) with vanilla.


> If you're using vanilla vim I don't think there's a whole lot neovim will offer you at present.

My vimrc is 80 lines, I don't feel it's vanilla at all, but I don't use :make or probably any other commands that launch subtasks so I guess this is what sets me apart.


I meant more with the plugins, but in any case regular vim isn't going anywhere either. I think there's eventually supposed to be hooks for building better GUIs and external integration, which will probably be the turning point when a lot more people switch over.


For me asynchronous plugins are a killer feature, which renders classic vim unusable for me.

I run linter every time I save, which made vim's UI lock for noticeable time on non trivially small files. With neovim linting is smooth as butter from UI/UX perspective. Also there is asynchronous make, and other possible features/plugins.


You can supposedly do Google docs style colaboritive editing with it (and the plugin supports Emacs and atom too).




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: