From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: cgit-lua: to jit or not to jit
Date: Tue, 14 Jan 2014 03:51:05 +0100 [thread overview]
Message-ID: <CAHmME9pBa6NH+cQFH+bbcFYkMYWKdpt_eS4UVVp+S-5p8sHu7w@mail.gmail.com> (raw)
In-Reply-To: <CAFBuAbcLEqfsS7KYRtd9nreg70nC=8-p5tEuRtz7KoceN=p2Yw@mail.gmail.com>
On Tue, Jan 14, 2014 at 3:37 AM, Andrew Starks <andrew.starks at trms.com> wrote:
>
> I don't have LuaJit installed and would not install it (and migrate
> everything I do over to it) just to use a library. By way of example, your
> library may as well have been written for Python, for as much good as it
> would be to me.
>
> By contrast, if you stick to the subset of 5.2 that 5.1 supports, and / or
> use a bit of the luacomp library, then anyone with lua 5.1, luajit or Lua
> 5.2 can use it.
>
> The question, from a user's perspective is: what benefit are you giving me,
> in exchange for locking me into luajit, as a dependency?
>
> Even if I am using Luajit, that doesn't mean that I don't need to support
> the current, mainline distribution and straight 5.1. So, I can't use your
> library as a dependency, if this were the case.
>
> It's easier for you if you like what the FFI gives you. Supporting the
> common subset and using luacompat, as necessary, is the simplest, for the
> user.
>
> IMHO, of course
That's a fairly compelling opinion. The only thing against it is the
temptation of using FFI in the default scripts that we ship with cgit.
But I suppose for the sake of giving users choice later on, it might
be best, as you've said, to continue to support both, and let the user
choose.
next prev parent reply other threads:[~2014-01-14 2:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 1:25 Jason
[not found] ` <CAF7MipWEwTYp2UJO8-kNoVDEK0mPCQFBay7pYeCZTrqKYevx6g@mail.gmail.com>
[not found] ` <CAHmME9pAXcyxypr0ogh4Or1DR-NBcyxDMed0m9uyu=6h=uRt5Q@mail.gmail.com>
2014-01-14 2:16 ` Jason
2014-01-14 19:53 ` fw
[not found] ` <B0F514CB-B748-48EA-B771-D557DEA82913@gmail.com>
2014-01-14 2:22 ` Jason
2014-01-14 2:37 ` andrew.starks
2014-01-14 2:51 ` Jason [this message]
2014-01-14 3:17 ` andrew.starks
2014-01-14 3:51 ` andrew.starks
2014-01-14 8:09 ` justin
2014-01-14 13:03 ` Jason
[not found] ` <20140114023403.GA31401@wilbur.25thandClement.com>
2014-01-14 2:45 ` Jason
2014-01-14 20:41 ` ewmailing
2014-01-14 20:50 ` chighland
2014-01-14 20:50 ` chighland
2014-01-15 1:32 ` malkia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9pBa6NH+cQFH+bbcFYkMYWKdpt_eS4UVVp+S-5p8sHu7w@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).