1. 22
  1.  

  2. 5

    Off-topic, and on a reluctantly curmudgeonly note this holiday season:

    Have you considered upgrading to neovim?

    I have. When Neovim was first launched I enthusiastically adopted it. I was already compiling my own Vim and managing a few patches of my own, so having to build from source wasn’t a big concern. And it was very promising. I tried to take every opportunity to spread the word, and to convince people that it’s in all our interests to encourage a minority fork, even those of us (myself included) who have no complaints with Vim.

    And yet, over time, my enthusiasm has waned. I started seeing inexplicable and subtle issues that I often would blame on my internet connection or my terminal emulator. To this day they’re too hard to file a bug report for. Neovim got a little over-enthusiastic with changing defaults. So upgrading Neovim became fraught, because I knew everytime that I was in for a context switch debugging my (fairly minimal) setup.

    I’m still glad Neovim happened. Mozilla and Firefox show that (unlike companies) open source projects never die. The advances it made in testing Vim are now available to anybody who wants to take them in a different direction. The lesson for future forks: be more conservative. Or maybe I’m just not the target audience? Maybe Neovim is working on expanding the adoption of modal editors, rather than taking marketshare from Vim. That gives me a more cheerful note on which to end; I wish them the best.

    1. 3

      this article really helped level-up my vim game; good stuff!