mikemike

9 ms·

1. 61.▲
   by mikemike 17y ago

   Mostly resolution and dispatch. Some of this needs very clever caching or the overhead can't be eliminated or hoisted. The control-flow constructs and iterators come to mind, too. The Rubyists certainly know about these issues, so you'll ha
2. 62.▲
   by mikemike 17y ago

   Spoiler: The Lua benchmark submissions are not parallelized.
3. 63.▲
   by mikemike 17y ago

   Some of Ruby's more excentric semantics are really hard to optimize away by a compiler. It takes a much greater effort to compile Ruby source code to machine code of similar quality than for Lua. Since time and money are not infinite reso
4. 64.▲
   by mikemike 17y ago

   For an apples-to-apples comparison you'll want to look at the single-threaded performance: http://shootout.alioth.debian.org/u32/benchmark.php?test=all...