Comment on Neovim 0.3 releasedparentComments−scribu8yThe main benefit of Neovim for me is support for async jobs.So, for example, if you have autosave enabled, it won’t block the UI while it’s writing to disk.−OscarDC8yVim now also supports async jobs since Vim 8 (but with a different API).IIRC, neovim implementation was first proposed as a vim PR before the fork happened. The mess following it was one of the main reason behind the fork.−DominoTree8yAt this point, vanilla Vim has async jobs as well, although it's not as clean as NeoVim−kerny8ycan you expand a bit more on "not as clean" as NeoVim? I consider vim's implementation of async jobs simpler than neovim's.
Comments
The main benefit of Neovim for me is support for async jobs.
So, for example, if you have autosave enabled, it won’t block the UI while it’s writing to disk.
Vim now also supports async jobs since Vim 8 (but with a different API).
IIRC, neovim implementation was first proposed as a vim PR before the fork happened. The mess following it was one of the main reason behind the fork.
At this point, vanilla Vim has async jobs as well, although it's not as clean as NeoVim
can you expand a bit more on "not as clean" as NeoVim? I consider vim's implementation of async jobs simpler than neovim's.