5 ms·

> They're already getting to the point of being two different editors with a common lineage and legacy support for Vimscript. Let's see how much traction Vimsc

by bhaak 3y ago

> They're already getting to the point of being two different editors with a common lineage and legacy support for Vimscript. Let's see how much traction Vimscript9 will get. From the distant view of an outsider I got strong NIH vibes from that. > it would probably have to be Vim basically winding down development. Doesn't seem likely. It depends on how much Bram was the main focus point of development and if the remaining contributors are able to transition to a less centric development structure. I would rather expect a EGCS/GCC "merger" than a true code merger. But only time will tell.

ftaghn 3y ago
> Let's see how much traction Vimscript9 will get. In practice, none. It's a wasteland. Extensions that aim to be compatible with both vim / neovim use the old vimscript, while lua has very, very significant traction in the neovim world among people who try to bring IDE like feature to vim. The amount of people willing to write extensions that only work on vim proper, which is what would happen if they used vim9script, is close to non existent. > I would rather expect a EGCS/GCC "merger" Or libav vs ffmpeg.
Legion 3y ago
> Let's see how much traction Vimscript9 will get. From the distant view of an outsider I got strong NIH vibes from that. Honestly, that's what most recent Vim development in the Neovim era looks like to me. Bram rejected async patches for years. Neovim gets made and proves out the demand for async. Vim suddenly is motivated to cook up their own, incompatible version of async. When Neovim began, I thought the inevitable future was the Vim project cherry-picking the best features from Neovim each time such a feature reached sufficient maturity and popularity, and merging Neovim's implementations back into the core project. I underestimated how strong the NIH syndrome was with Vim proper.

by bhaak 3y ago

ftaghn 3y ago

> Let's see how much traction Vimscript9 will get. In practice, none. It's a wasteland. Extensions that aim to be compatible with both vim / neovim use the old vimscript, while lua has very, very significant traction in the neovim world among people who try to bring IDE like feature to vim. The amount of people willing to write extensions that only work on vim proper, which is what would happen if they used vim9script, is close to non existent. > I would rather expect a EGCS/GCC "merger" Or libav vs ffmpeg.

Legion 3y ago

> Let's see how much traction Vimscript9 will get. From the distant view of an outsider I got strong NIH vibes from that. Honestly, that's what most recent Vim development in the Neovim era looks like to me. Bram rejected async patches for years. Neovim gets made and proves out the demand for async. Vim suddenly is motivated to cook up their own, incompatible version of async. When Neovim began, I thought the inevitable future was the Vim project cherry-picking the best features from Neovim each time such a feature reached sufficient maturity and popularity, and merging Neovim's implementations back into the core project. I underestimated how strong the NIH syndrome was with Vim proper.