Yes, perhaps if the CLI tool is being invoked many many times in succession.
But otherwise JITing isn't an issue: either (a) your program runs quickly in which case the Ignition interpreter is used and the JIT is not used, or (b) your program runs slowly in which case JIT (Sparkplug/Maglev/Turbofan) has time to warm up.
> Yes, perhaps if the CLI tool is being invoked many many times in succession.
Each execution will be a fresh VM though. A CLI tool isn't a long-running daemon. There is also the whole lack of parallelism without forking in this ecosystem.
a) It's actually calling some native code internally (i.e. rust, c/c++ or V8 internals)
b) JIT'ed
Path "b" is very hard to achieve in CLI tool