vim-startuptime VS vim9jit

That is native and inbuild but I would suggest below options instead 1. Using lazy's Profile tab instead https://github.com/folke/lazy.nvim 2. Using a dedicated plugin to do this https://github.com/dstein64/vim-startuptime. 3. Using an external program hyperfine is one that I use https://github.com/sharkdp/hyperfine

This plugin https://github.com/dstein64/vim-startuptime

dstein64/vim-startuptime (which I never use, my startup time is under 130ms, which is sufficient)

Use the plugin with the flag --tries 100. Also, what are the first 10 lines of output from running the above command? I'll start.

only today I tried this plug to test startup time and got this result:

dstein64/vim-startuptime: ⏲️ A Vim plugin for profiling Vim's startup time.

Using vim-startuptime to profile, I get these startup numbers on an Apple M1 Macbook:

Oh sorry, I already solved my issue but forgot to delete the post! But to answer your question: Of course! It's https://github.com/dstein64/vim-startuptime. You can either launch nvim with nvim --startuptime outputfile.log FILENAME to get detailed diagnostics in the file outputfile.log or just call :StartupTime after nvim/vim has started up to get this graph. It's pretty neat and easy to use!

You could try to install this plugin temporarily : https://github.com/dstein64/vim-startuptime

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.