Seriously??
Outperforming optimised C is basically impossible for any JIT.
Theoretically, a JIT can do better because it can know more specifics but in practice it just doesn't happen.
Outperforming optimised C is basically impossible for any JIT.
Theoretically, a JIT can do better because it can know more specifics but in practice it just doesn't happen.
Doesn't mean it did the same amount if work or even uses the same algorithms and data structures but it did achieve the same end goal.
Unfortunately comparing two "languages" in the way it was done in this paper only seems to prove that for the subset of edgecases the author needed to handle his Ruby implementation could make tradeoffs that are quicker than the off the shelf C extention.
Had he then went on to actually rewrite the code that was a bottleneck in C making the same tradeoffs it might have been