3 ms·
This is really a rant about the vim community and your experience there, rather than a write-up of why neovim is better than vim. As an end-user, the only reas
by mod 12y ago
This is really a rant about the vim community and your experience there, rather than a write-up of why neovim is better than vim.
As an end-user, the only reason you gave me was "some new plugins," and didn't even speak to the power or improvements those plugins make.
Retitle "My Bad Experience with Vim contribution and Bram M."
That said, it was a pretty interesting read.
- peatmoss 12y agoI use a lot of technologies based on criteria that aren't all grounded in features. I do happen to appreciate knowing that I could modify some code for the benefit of many, and without the epic burden of maintaining a fork. There's also a network effect, in that I'm more likely to use software that I perceive to have a large and qualitatively friendly group of users / developers. The article might not have addressed specific technological feature benefits, but it certainly articulated some desirable sounding community features. If I hadn't previously moved to the land of emacs, I'd probably be moving to Neovim.
- ggreer 12y agoGood points. A better codebase and community typically mean a better experience for users, but I avoided talking much about concrete benefits because I thought the post was getting rather long. There are a lot of opportunities for improving the responsiveness of plugins. Many currently block the UI in Vim: autocomplete, search, ctrlp-style filename matching, etc. The list of Neovim-only plugins isn't huge yet, but it's only going to grow longer as plugin writers take advantage of Neovim's improved API.