News for hackers. Stuff that matters.

A comment on Neovim Conf 2022. Parent comment

Re:Neovim Conf 2022 by halostatue on Friday December 09, 2022 @10:36AM (#33922400)
The Neovim hard fork is not fully compatible, nor is it always better performing. I also do not find that Lua is better for scripting overall, because there is an impedance mismatch when you need to interact with the editor model. (If you’re doing just programming then, yes, it’s better. But it’s the interface layer which is difficult, and which I find worse than Vimscript or Vimscript9.)

MacVim is a macOS packaged version of Vim with (fairly) light customizations of gvim which is part of the vim source bundle. All neovim GUIs are from-scratch constructions because the neovim developers decided that they did not want to support GUIs directly. IMO, this was a mistake, because none of the neovim GUIs that exist work as well or are as well OS integrated as gvim or make for as "easy" packaging as MacVim has.

[ Parent | on HN ]
Re:Neovim Conf 2022 by cge on Friday December 09, 2022 @11:33AM (#33923216)
Neovim also has some surprising feature regressions compared to Vim. I tried switching to neovim for a while until I realized it was silently removing all ACLs on edited files and breaking services for me. Looking into it, I found that, for no clear reason, ACL handling was removed early on in neovim, and a bug had been open about it, with multiple pull requests that were never merged, since 2014 (https://github.com/neovim/neovim/issues/1200). Vim has never had a problem with this, as far as I know.
[ Parent | on HN ]
Re:Neovim Conf 2022 by Jorengarenar on Friday December 09, 2022 @11:50AM (#33923470)
My favourite is "it's not a bug, it's a feature" under issue reporting broken bang commands (https://github.com/neovim/neovim/issues/1496)
[ Parent | on HN ]