|
|
|
|
|
by mempko
3571 days ago
|
|
I wasn't talking about Thiago's credentials. I was talking about the tone in his reply which was clearly abrasive. Brams criticism is valid about Thiago solution. Forcing msgpack is less than ideal. It's clear Thiago is learning as he goes along. Taking his work without reflection would be silly. Also it is also clear neovim wants plugin writers. So they want vim to be compatible with what they made so they can grab users. Why should vim care about being compatible with neovim? |
|
As for why vim should care? Because at this point I'd put money on neovim as the long term winner, and if I were Bram, I'd worry about vim joining vi on the sidelines as 'still developed, still in use, but not the vi everyone uses when they log into a linux box'. I'd look at my codebase and neovim's, at my toolchain and neovim's, at my community and neovim's, at my velocity and neovim's, and I'd imagine neovim eclipsing vim over time.
Maybe that's fine. But Bram is hardly some god-king who's position as foremost developer in the vi universe is a lifetime appointment--especially after he took that position from Bill Joy.