> > 0) Port LuaJIT to Lua 5.3. That alone would probably solve most of the > issues. I'd love to see this or at least a fork of LuaJIT that tries to keep up with current Lua. I don't know how hard that would be.