Ну так давайте же послушаем разработчиков plugins (и сходные высказывания можно найти и со стороны других)!
Цитата из
https://www.reddit.com/r/vim/comments/f8a48t/vim_or_neovim/ , пишет skywind3000:
As a plugin developer, vim has better API, neovim seems "new" but many features are not detailed enough:
1: floatwin's patch: takes about 2 years to get merged, but still lack of many features like: z-index and borders. popup-win has not only z-index and borders but also can be dragged by mouse, can be resized or closed by mouse.
2: terminal API: both termopen() and :term in neovim are too simple, compared to term_start in vim, termopen has less functionality and options. jobstart still can't pass arguments precisely on windows but job_start can.
3: neovim's developers seem afraid of writing documentation, nvim_terminal_emulator.txt has 388 lines, while terminal.txt in vim has 1440 lines. Many neovim APIs have poor documentation, such has job-apis and floatwin-apis. I can't believe floatwin-apis's doc is only 120 lines (:h api-floatwin and :h nvim_open_win), many problems I encountered in floatwin have no solution or even a single clue in their docs, I had to google them and finally found something in the issues. But popup.txt in vim has 1041 lines, it is really helpful and rich in details, I don't need to google anything after reading it.
4: I still can't figure out a proper way to detect is neovim running in a GUI? (since has('gui_running') is abolished in neovim), I know, neovim developers have their own choices, but please, just give me a straight forward way for this, and I can delete the following ugly code from my vimrc.
<ужасный неокод вместо has("gui_running") пропущен>5: Incomplete features, if what I remember is accurate, neovim once promised translate vimscript into Lua to make it run faster, can someone give me some updates for this?? Yes, we have floatwin now, but floatwin rendering is really inefficient, popup-win draws 3-4 times faster than floatwin.
