On Tuesday, February 9, 2016 at 4:36:48 PM UTC-3, Christian Brabandt wrote: > Thanks for the constructive feedback. I appreciate it, that you as the > Neovim creator give feedback here.
Hi Christian, I also appreciate you taking notice. > It's also appreciated, that certain > bugs, which have been found when developing Neovim have at least found > their way back to Vim itself (although, that communication could be > improved). I'd like to improve communication and hope that my experience in adding asynchronous events to Neovim helps the Vim community to avoid some of the mistakes I made. I also would welcome the Vim community to engage more in Neovim development, even if it is only to use it as a "test bench" for new features that could be integrated back into Vim. > I can only speak for myself, but I think it would be appreciated by the > Vim/Neovim user community, if the API is at least standardized, so that > not every plugin writer needs to either decide whether he wants to > support Vim or Neovim or has to work around the particularities in both > applications. My thoughts exactly. In a previous [message](https://groups.google.com/d/msg/vim_dev/_SbMTGshzVc/XZEXxaxDDQAJ) I said: > I will be glad to add a compatibility layer to Vim's channel feature if plugin > authors start to use it, but unfortunately I can't do the same for this job > control API as it will only make things harder for users. Tha doesn't mean we are unwilling to discuss changes in Neovim job API. On the contrary, we are open to standardizing it, but we need to carefully examine the strengths and weakness of each interface before making harsh decisions. The reason I said we would not follow Vim is because I honestly felt that the job proposal for Vim was a regression when compared to what we have in Neovim(and I know many plugin developers that use it will agree with me), but could be convinced otherwise with arguments and examples. > Since you seem to know both interfaces, would you be willing to > contribute a patch, that will help develop a consistent interface as far > as this seems feasible? Bram, since you are actually working on that > part of the code, can we assume, that you would look into such a patch > and help the community to have at least some kind of consistent > interface for its users? As I said in the previous post, yes, I'm willing to update my old patch to Vim, possibly making changes to the API(should we reach an agreement on it). But I need to wait Bram's response, as so far I've had pratically no feedback from him(and one can only have so much faith). > I really hope, that we can find a way, to work together and specify the > details of those interfaces which would gain the users a lot. So let's > not have personal prejudice get in our way! (I don't want to see more of > those angry discussions, as its happening currently at reddit, so let's > just make the best for all users). Same here! It is not unreasonable to think that Neovim had a major impact in Bram's decision to implement the channel/job features, and that thought also gave a bump into my motivation for making Neovim even better. This confirms that competition is only good for everyone, but there's no reason we can't do it in a friendly way, don't you think? So, instead of wasting our time with angry discussions, let's join forces and focus on the "real enemy": Emacs!(jk hahaha) Before I finish, let me quote something LCD said in a previous message: > I don't really understand what problem do channels solve, or where is all this heading. This says everything: we should focus on solving the problem rather than simply adding new features without a proper plan. Since you were so friendly, I will later post another message that expands my reasoning as to why I think Vim should focus on job control(at least for now). Thanks again Chris! Thiago. -- -- 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.
