I have had similar thoughts, and have even theorized that the two would merge at some point. But that said, The goals of the two projects are still pretty diffe

I have had similar thoughts, and have even theorized that the two would merge at some point. But that said, The goals of the two projects are still pretty different. It sounds like Vim proper is going to start receiving More new features, but overall it still has a significant focus on stability. I do wonder if that will shift as the new maintainers get more and more confident and capable in the code base. Once that occurs, I suspect that neovim will start to look really good, even perhaps including to the vim proper maintainers. What might be a big difference though and a big enough stumbling block to prevent merging is the fact that neovim code base has been refactored extensively and updated. Having worked in a big project that was refactored without me, and then returned, it is actually worse than a new code base because you feel like you should know where things are, but they aren't there. It continually misleads you and wastes your time. I could see that frustration being enough to keep the them proper people from merging or moving to neovim.