http://blog.reverberate.org/2009/02/09/disappointment/
To make a long story short, porting my existing Lua project to use my Ruby-like method dispatch resulted in a 4x slowdown.
Past discussion: http://news.ycombinator.com/item?id=617278
If you want to learn Lua, Ierusalimschy's _Programming in Lua_ (http://www.inf.puc-rio.br/~roberto/pil2/) is by far the best book. Lua is one of my favorite languages. While it's good on its own, you'll get a lot more out of it if you're comfortable with C. Lua+C is an excellent combination.
Lua Performance Tips: (http://www.lua.org/gems/sample.pdf)
A No-Frills Introduction to Lua 5.1 VM Instructions: (http://luaforge.net/docman/view.php/83/98/ANoFrillsIntroToLu...)
Ease of implementation has a multiplier effect with Open development effort. Not only do you get more of "more eyeballs," new contributors can ramp up faster. There tends to be a better effort/ fun ratio.
Even the Ruby lexer is full of weird edge cases.
Actually, the lexer sets state that changes the operation of the parser and vice versa.
But also, Lua was always designed with cleanness and simplicity of implementation in mind. Its developers have strong backgrounds in both theory and engineering, which you can see in their interview in the book Masterminds of Programming. They've been very conservative about the design of the language. In contrast, Ruby feels much messier and more "evolved" - look at its Yacc grammar[1], for example, compared to the grammar of JavaScript or Lua[2]. Even the Ruby lexer is full of weird edge cases. Much of MRI is like that, and for years it was the only "spec" for the language; now its decisions have been reverse-engineered and inherited by all other implementations.
[1]: http://blog.nicksieger.com/articles/2006/10/27/visualization...
[2]: http://www.lua.org/manual/5.1/manual.html#8
[By the way, I've used Ruby for years and like it at lot, while I've written only a few lines of Lua code and like it but am not deeply familiar with it.]