Hacker News Reader

You could ask the same question about why he decided to make the async api and terminal mode incompatible with existing equivalents in neovim. Sadly, the ecosystem seems to be splitting more and more between vim and neovim.

View on HN

My impression is that Bram is trying his best to outcompete neovim.

That goes without saying, and it's just unfortunate that he chooses to compete rather than collaborate

Competition is good, and it’s the reason why Neovim was created in the first place!

I mean, the reason is that those async patches were just sitting in the queue for a year, and by starting Neovim, they could get them in right away.

Then Bram started competing afterwards.

Those patches were broken to begin with when submitted to Vim, and never got fixed until NeoVim was forked out of the blue. People generally don’t know the details of this, and blindly blame Bram.

Why did it take neovim being forked to get those patches fixed?

Is there evidence that the fork was the root cause of that action. and not a mere coincidental correlation?

Reply on news.ycombinator.com