News for hackers. Stuff that matters.
Re:Ruby 2.1: Out-of-Band GC by mcguire on Thursday January 30, 2014 @04:03PM (#7153340)
"dynamically typed, bytecode compiled"

I haven't followed Ruby development, but the last time I heard, Ruby 1.8 and prior was a tree-walking interpreter---simple to implement but not fast at all.

Re:Ruby 2.1: Out-of-Band GC by srd on Thursday January 30, 2014 @04:41PM (#7153526)
This changed in 1.9. Ruby is now compiled into a stack machine based bytecode. Ruby 1.8 used the AST internally, you're right there. This made e.g. method calls very slow compared to the new byte code representation.
Re:Ruby 2.1: Out-of-Band GC by steveklabnik on Thursday January 30, 2014 @04:50PM (#7153557)
1.8 -> 1.9 was an entire re-write, it's now a bytecode compiled language: http://www.ruby-doc.org/core-2.1.0/RubyVM/InstructionSequenc...
Re:Ruby 2.1: Out-of-Band GC by munificent on Thursday January 30, 2014 @04:41PM (#7153522)
That's correct. I still think Ruby 1.8 would be a useful data point just because it's a widely used language that many people are familiar with, but in this case I'm comparing it to Ruby 2.0, so it is apples/apples.

For what it's worth, I look at these benchmarks as validating feasibility more so than really trying to win some performance fight between languages. In order to argue that my language is suitable for real world use, I need to show it's performance is comparable to other languages that are widely used. From that angle, Ruby is a fine comparison, regardless of how it's implemented.