From mboxrd@z Thu Jan  1 00:00:00 1970
From: chighland at gmail.com (Coda Highland)
Date: Tue, 14 Jan 2014 12:50:09 -0800
Subject: cgit-lua: to jit or not to jit
In-Reply-To: <CA+Q62MBUjVXmQWyMuMUAgaPqfKVVNRKy1eMm9Sn23ChAspoiiQ@mail.gmail.com>
References: <CAHmME9oAUNM-dF8Bq3E6omDqSfx5fExriTFr=W0rszdZ6WYpLQ@mail.gmail.com>
 <CA+Q62MBUjVXmQWyMuMUAgaPqfKVVNRKy1eMm9Sn23ChAspoiiQ@mail.gmail.com>
Message-ID: <CAFE_sBHknnH_VAMebGzvk05T6b00T1BhbXs73gJPNNwUKBjVXg@mail.gmail.com>

On Tue, Jan 14, 2014 at 12:41 PM, Eric Wing <ewmailing at gmail.com> wrote:
>> But perhaps there
>> are some obvious downsides to this approach that I also am missing.
>
> Here are a few more potential downsides not mentioned so far.
>
> One is that iOS and Windows Store policies disallow JIT. While you can
> disable this part in LuaJIT, most of the performance advantages
> disappear when you do this.

However, even with the JIT disabled, LuaJIT does tend to outperform
Lua for a lot of use cases (Lua wins in a few cases) just by virtue of
having an interpreter written in hand-tuned assembly.

/s/ Adam