Sorry I'm late to this party... I'm an Nmap developer that is casually interested in git development. I've been lurking for a while and thought I'd post my thoughts on this thread.
On Sun, Nov 25, 2012 at 6:25 AM, Nguyen Thai Ngoc Duy <pclo...@gmail.com> wrote: >> The most important issues to consider when imagining a future with a >> hybrid of code in C and some scripting language "X" are: >> >> * Portability: is "X" available on all platforms targeted by git, in >> usable and mutually-compatible versions? >> >> * Startup time: Is the time to start the "X" interpreter prohibitive? >> (On my computer, "python -c pass", which starts the Python >> interpreter and does nothing, takes about 24ms.) This overhead would >> be incurred by every command that is not pure C. >> >> * Should the scripting language access the C functionality only by >> calling pure-C executables or by dynamically or statically linking to >> a binary module interface? If the former, then the granularity of >> interactions between "X" and C is necessarily coarse, and "X" cannot >> be used to implement anything but the outermost layer of >> functionality. If the latter, then the way would be clear to >> implement much more of git in "X" (and lua would also be worth >> considering). >> >> * Learning curve for developers: how difficult is it for a typical git >> developer to become conversant with "X", considering both (1) how >> likely is it that the typical git developer already knows "X" and >> (2) how straightforward and predictable is the language "X"? >> In this category I think that Python has a huge advantage over >> Perl, though certainly opinions will differ and Ruby would also be >> a contender. > > * We might also need an embedded language variant, like Jeff's lua > experiment. I'd be nice if "X" can also take this role. Lua has been an incredible success for Nmap [2](and other projects). As an embedded scripting language, it's unrivaled in terms of ease of embedding, ease of use for users, and performance. I would strongly recommend the git developers to seriously consider it. Addressing the points listed above: >> * Portability: is "X" available on all platforms targeted by git, in >> usable and mutually-compatible versions? Lua is written in ANSI C and so compiles basically anywhere (certainly anywhere git does). >> * Startup time: Is the time to start the "X" interpreter prohibitive? >> (On my computer, "python -c pass", which starts the Python >> interpreter and does nothing, takes about 24ms.) This overhead would >> be incurred by every command that is not pure C. As mentioned elsewhere in this thread by Joshua: "Because Lua was mentioned in another message of this thread, I'll provide the following: * A cold run of 'lua5.1 -e ""' takes 0.4 seconds. The second run takes 0.03 seconds. * A cold run of LuaJIT takes the same." The runtime figures would probably be much lower if git modules (e.g. pull) were capable of calling other modules without forking, all within the same Lua environment. >> * Should the scripting language access the C functionality only by >> calling pure-C executables or by dynamically or statically linking to >> a binary module interface? If the former, then the granularity of >> interactions between "X" and C is necessarily coarse, and "X" cannot >> be used to implement anything but the outermost layer of >> functionality. If the latter, then the way would be clear to >> implement much more of git in "X" (and lua would also be worth >> considering). Using Lua as a glue between a proper git C API and modules would be optimal in my opinion and experience. >> * Learning curve for developers: how difficult is it for a typical git >> developer to become conversant with "X", considering both (1) how >> likely is it that the typical git developer already knows "X" and >> (2) how straightforward and predictable is the language "X"? >> In this category I think that Python has a huge advantage over >> Perl, though certainly opinions will differ and Ruby would also be >> a contender. Lua is remarkably easy to learn and is engineered so it's approachable by novice (or non-) programmers. Still, it offers all the features you expect from a modern scripting language including GC, real lexical scoping and closure, tables/arrays, and *coroutines*. While Nmap occasionally gets questions about why we didn't use Python, no one complains about Lua itself. As for version considerations, Lua changes at a glacial pace compared to other popular languages like Python or Ruby. Lua 5.2 was released last year and 5.1 was released 5 years before that [1]. Still, while users (people who bind Lua to applications) are certainly encouraged to upgrade Lua, there is no real need to. Binding Lua to an application statically is not a significant cost as it compiles to less than 200 KB including base libraries; so, it's simple and cheap to remain independent of the system git runs on. It isn't unreasonable -- indeed, it is common -- to select one version of Lua and keep it for a significant lifetime of the project. [I'd be happy to answer any questions concerning Lua and/or scripting Git. I'd also be happy to assist in embedding Lua in Git.] [1] http://www.lua.org/versions.html [2] http://nmap.org/book/nse.html -- - Patrick Donnelly -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
