What I'm sad about is that JavaScript is so locked-in on the browser that I can't use Lua there as well.
What I'm sad about is that JavaScript is so locked-in on the browser that I can't use Lua there as well.
As for fast, I would love to see more comparisons on real-world code, there are too few on the web.
It is easier to embed Lua than JavaScript, however, that's say a week of work, then you're done, so it isn't a reason for something like Wikipedia to prefer Lua.
With all that said, Lua and JavaScript are both good languages, adding either one to Wikipedia is going to be a huge improvement.
edit: looks like my phrasing has offended mikemike, who I have the utmost respect for, so I removed some stuff he disliked.
(When doing things like "given an interval of indices a-to-b, partition it into n subintervals so that every element of the original interval is in precisely one of the sub-intervals, and the lengths of the intervals are either the same or as close to each other as possible", I find the "count from one, bounds are inclusive" model horrible. How do you express an interval from a with the length of zero? It's just <a,a) with half-open intervals. What, <a, a-1>? So many special cases with the <a, b> model...)
Watch the YouTube video of the Wikipedia presentation linked elsewhere in this discussion.
From the video, they picked Lua also because they could have multiple concurrent Lua states (no globals), easy to override the default memory allocators for security, Lua VM instances are very cheap and fast to create and launch, and the code base was small enough that their security guy could actually audit all the code (and they even submitted a patch).
All these properties are hard to find with Javascript, but with Javascript, you have to go further and first decide which Javascript implementation to use. The ECMA spec says nothing about C interfaces or embedding so every Javascript engine (e.g. V8, JSCore, SpiderMonkey) is completely different.
They also said they are using the standard Lua interpreter and not LuaJIT because stock Lua happened to already be really fast and fast enough for their purposes right now.
I didn't say otherwise, I know LuaJIT is used. What I did say was I have not seen speed comparisons on such real-world code - but I would love to see a link if you have one.
> and the code base was small enough that their security guy could actually audit all the code
A small codebase is indeed good, but JavaScript VMs have very large teams of people working on hardening them, both reading and reviewing the code and applying methods like fuzzing to look for security problems. The fact is that JS VMs are likely the more hardened of anything out there, simply because they are used in web browsers.
> with Javascript, you have to go further and first decide which Javascript implementation to use.
Lua has at least two implementations as well, mainstream Lua and LuaJIT.
> They also said they are using the standard Lua interpreter and not LuaJIT because stock Lua happened to already be really fast and fast enough for their purposes right now.
That's cool.
The difference is that the Lua C API is standardized meaning that C code can work with either just fine. The only big incompatibility problem is that LuaJIT provides an extra, non-portable, FFI library in addition to the standard one.
Only to programmers raised in a C-based world. Normal people, mathematicians, and Lua start counting at 1.
I remember when I was new to programming I was horribly annoyed by the fact that C started counting at 0 - that was so unnatural! (the BASIC I had used up until that point used 1-based indexing too)
0-based indexing is good for low-level code, for memory and screen addresses. For high level concepts starting at 1 is the natural choice.
However, I admit after many years of C/C++ I was quite irritated by everything starting at 1 by default. My brain adapted after a few days, though.
I think the Lua devs made the right choice with the 1-based indexing. Just like 0-based indexing was the right choice for C. As I said both ways are natural but in different scenarios: 0-based for low-level machine code, 1-based for high level human concepts.
I mostly agree, except for mathematicians ;) , where it depends on the context. For example aleph numbers start at 0,
http://en.wikipedia.org/wiki/Aleph_number
and even the natural numbers can start at 0 or 1,
Large standard libraries would mean huge potential for security holes in this case; they've locked features down to only support things that they could make secure.
And starting from 1 you can get used to. LuaJIT doesn't even REQUIRE you start from 1; it'll optimize arrays you start from zero. And even vanilla Lua will accept 0 as a table index; it just won't treat it as an array (for ipairs() or length).
But if you start asking people for complaints about JavaScript, you will find people complaining about operators acting wonky, auto-type-conversion problems from hell, and even odder things like [1].
Lua is just a cleaner design. I am stuck using JavaScript when I want to work on the web, but knowing what an elegant language CAN be makes me enjoy it a lot less. And don't get me started on how ugly NodeJS is because JavaScript doesn't have coroutines...