Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
Yuioup
on Jan 1, 2022
|
parent
|
context
|
favorite
| on:
Vim9 Script Feature-Complete
My impression is that Bram is trying his best to outcompete neovim.
mi_lk
on Jan 1, 2022
[–]
That goes without saying, and it's just unfortunate that he chooses to compete rather than collaborate
BooneJS
on Jan 1, 2022
|
parent
[–]
Competition is good, and it’s the reason why Neovim was created in the first place!
Tyr42
on Jan 1, 2022
|
root
|
parent
[–]
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.
bitigchi
on Jan 2, 2022
|
root
|
parent
[–]
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.
dolni
on Jan 2, 2022
|
root
|
parent
[–]
Why did it take neovim being forked to get those patches fixed?
voakbasda
on Jan 3, 2022
|
root
|
parent
[–]
Is there evidence that the fork was the root cause of that action. and not a mere coincidental correlation?
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: