I can just speak for myself: VAM/vundle/neovim -> all were created because people didn't know each other well.
Managing community. But that's different question, eg trends.google.com vim vs 'visual studio code' (critical mass .. potential future problem) For instance for PHP https://github.com/MarcWeber/editor-cells I spent 3 days on trying to embed any PHP completion engine. But failed with all. Eclim is little bit slow, the other ones based language-server-protocol https://langserver.org/ versions didn't work. Small things could be improved, eg sharing compile formats https://github.com/MarcWeber/vim-addon-errorformats -> yet it doesn't work once you want to support compilation server (editor-cells support eg typical --watch implementations) -> so having to redo all work eg in python to feed quickfix. Another thing is $VIMRUNTIME .. keep or turn into plugins to enable faster iterations ? So while editor-cells tries to implement stupid message passing so that you can run multiple tools at the same time even using multiple processes (multi core support), its also adding much debugging overhead and problems of its own kind. Which voting is best? You could also introduce 'money voting' and spend 20% to charity (store like) -> if people can make a living from plugin writing things will get done automatically. .. just some thoughts Marc Weber -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
