Vim VS vim9jit

There have been six releases of Vim _this week_. So, no, Vim is not "dead".

https://github.com/vim/vim/tags

Vim

We wanted this machine to be as lean as possible. There is only so much memory and processing power to go around. Remember, our machine has 3 GHz Dual-Core Intel Core i7 processor with 16 GB 1600 MHz DDR3 memory. We also wanted as much of that space and power to be used for serving up our web applications. However, we also wanted to have an additional option for editing any code files, in addition to vim.

Vim: winget install vim.vim

So Raylib library could be your best option. Let's code, just open your text editor like vim or VSCodium in your Windows, Linux or Mac computer and let's build our indie game with Raylib library, no extra dependencies are needed.

nevermind, after a little searching, I found the solution, this isn't 'a nvchad problem or neovim problem, but a vim problem, and this github issue explains it. In the bottom of the issue, someone did post a fix here, but I haven't really tried it.

Then I went to official vim GitHub and looked around and it also had only instruction for installing vim from scratch.

When you said Vim, I thought you were talking about Vim (a code editor). Clearly not haha

That's not happening any time soon, but there's this project by one of Neovim's contributers that transpiles Vim9 script into Lua.

Probably feasible with https://github.com/tjdevries/vim9jit actually

There's https://github.com/tjdevries/vim9jit. It has reportedly been used to port Vim9script runtime files to Neovim.

Neovim is going to use a transpiler that covers vim9script code to lua code using the nvim api in the future (https://github.com/tjdevries/vim9jit)

I didn’t watch the streams because I wasn’t totally sure what he was even doing, but maybe this will take some of it off your hands: https://github.com/tjdevries/vim9jit

It could (rightly) be argued that neovim could just merge in vim9script, but I think this probably isn't the best more. I'm personally more in favor of getting a vim9 cross-compiler working, that way there's an easy way to support both. But that's my ignorant two cents on the matter.

A core contributor to Neovim is toying with a Vim9Script to Lua convertor.

That's not necessarily true.

Core maintainer of the Neovim Tjdevries is working on a compatibility layer that would allow vim9 to not only run in Neovim, but likely faster.

Source: https://github.com/tjdevries/vim9jit

My understanding was the neovim folks decided this wasn't work the hassle. TJ already has https://github.com/tjdevries/vim9jit, which transpiles vim9scripts to lua, and that is much more likely the way things will go.