Re: cgit-lua: to jit or not to jit

[Tim Hill <drtimhill@...>]

On Jan 13, 2014, at 5:25 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi folks,
> 
> Over at the cgit project [1], we're in the process of adding Lua
> support. Things are going swimmingly, and I've just merged to the
> master tree some commits adding full lua support [2] to our filter API
> [3] and an example script [4]. At the moment we've got some moderately
> messy logic in our makefile [6] that autodetects if LuaJIT is
> installed, and if it isn't, falls back to mainline Lua.
> 
> What I'm wondering is -- what is the purpose of keeping around support
> for mainline Lua? Why shouldn't we just go with LuaJIT and be done
> with it? I'm unable to find any advantages mainline Lua has over
> LuaJIT, which is why I'm emailing these lists. What features am I
> forgetting about that would make some people prefer mainline Lua over
> LuaJIT?
> 

LuaJIT is currently compatible with Lua 5.1, not 5.2 or the upcoming 5.3, and my understanding is the LuaJIT project has now forked from mainstream Lua and will not be staying in sync with anything past 5.1, so I would expect over time the two to diverge.

—Tim