Vim9 Script Feature-Complete

Re:Vim9 Script Feature-Complete by Tyr42 on Saturday January 01, 2022 @04:22PM (#29762971)

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.

[ Parent | on HN ]

Re:Vim9 Script Feature-Complete by bitigchi on Saturday January 01, 2022 @10:30PM (#29765513)

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.

[ Parent | on HN ]

Re:Vim9 Script Feature-Complete by dolni on Sunday January 02, 2022 @12:02PM (#29770511)

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

[ Parent | on HN ]

Re:Vim9 Script Feature-Complete by voakbasda on Monday January 03, 2022 @10:46AM (#29781891)

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

[ Parent | on HN ]