>Beyond the purist ideal of understanding the whole stack, this has practical implications. When you find a bug in LuaJIT, understanding it and fixing it is terribly complicated.
Well, how often people fix bugs in the compiler they use (and haven't written themselves)? Doesn't seem as much a "practical" consideration as the author says...
>Another issue is that PUC Lua and LuaJIT are diverging. LuaJIT implements Lua 5.1. Lua 5.2 code can be made to work as long as it does not use _ENV, but code that leverages the new features in Lua 5.3 is not supported at all
Well, not as much diverging as in "going to different directions" as that LuaJIT implements an older version. Isn't it supposed to eventually catch up?