vim-win32-installer VS vim9jit

There are official 64-bit Windows builds, you can find them here, for example: https://github.com/vim/vim-win32-installer/releases

I have no idea, but why wait? There's nothing tricky about installing nightly (I called them current in my original reply) versions. Here's a link to a Windows executable. https://github.com/vim/vim-win32-installer/releases

gVim

This is with gvim builds from vim-win32-installer?

This is already part of the official Vim (through the patches). The various Linux distributions and MacOS ship Vim with various patches. So this will be available whenever these distributions decide to include this patch. If you want to use the latest Vim without waiting for the official distribution, you can download it from: Windows: https://github.com/vim/vim-win32-installer/releases MacOS: https://github.com/macvim-dev/macvim/releases Linux: You can build the latest sources.

You can install the latest Vim release from https://github.com/vim/vim-win32-installer/releases. This installation includes vim.exe (terminal Vim for MS-Windows).

Yes, filesystem redirections are generally in place for 32-bit programs on 64-bit Windows. Another option instead of using sysnative is to install the 64-bit version of vim. That's what I do anyway. You can get it at https://github.com/vim/vim-win32-installer/releases and download the 64-bit versions.

Windows Releases: https://github.com/vim/vim-win32-installer/releases/tag/v9.0.0000

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.