On 01/06/2010 06:27 PM, Marnen Laibow-Koser wrote:

> Devil's advocate: *is* Ruby the right tool the job for thoses cases? 
> Obviously, I'd rather write in Ruby than in C* or Java, but in a case 
> where the use of Ruby leads to performance problems, Ruby is probably 
> ipso facto not the right tool for the job.

Before you can make that judgement you need to find out the reason for 
slowness.  A flawed design might be faster in C but fixing the design in 
Ruby might yield even better performance.

> I can well believe that, though I had understood that some of Python's 
> speed boost came from bytecode compilation as well.

http://en.wikipedia.org/wiki/YARV

	robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/