1. 17
  1.  

  2. 8

    Whenever I see json-rpc I mentally translate to SOAP, and whenever I ask myself if my editor needs to be using SOAP…

    Deleting VMS support, on the other hand, is a change I can get behind.

    1. 3

      Here is Bram Moolenaar’s response (maintainer of Vim) https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby8

      1. 1

        In general, vim’s point of strength is being hacker-friendly in the interface: even if commands are not always consistent, they are very practical, and aim to become like an extension of your body.

        Even if I would not have lots of fancy plugins, I would still use vim just because of things like . (repeat command) or the command-movement combo.

        Sure thing, getting rid of deprecated stuff is a good idea, and maintainability is important, but what we don’t need is another eclipse…

        1. 2

          Don’t worry, Neovim doesn’t plan to change any of the basic features of Vim, or any of the built-in commands. From the README:

          It is important to emphasize that this is not a project to rewrite vim from scratch or transform it into an IDE (though the new features provided will enable IDE-like distributions of the editor). The changes implemented here should have little impact on vim’s editing model or vimscript in general. Most vimscript plugins should continue to work normally.

          This project only directly affects plugin developers and Vim developers, not end-users. But Neovim will make it more likely that people will build cooler plugins, so it will affect end-users indirectly. And some end-users might turn into plugin developers because developing plugins will be easier in Neovim.