Having lived in Ruby code for a bit, I think it's fair to say that you're entirely right. It's immature, it's poorly profiled, it has memory leaks, and the scoping rules are a nightmare.
But it sounds like you were doing profiling and optimization early and often, which might have been premature, and thus might have been a waste of time.
Who's to say? Ruby isn't for everyone. Perhaps your ideal web stack is what you're using. (What're you using, btw?) I've been itching to use Haskell for a webapp.
"Perhaps your ideal web stack is what you're using. (What're you using, btw?)"
He has stated in previous comments that he's using scala.
Interestingly, merb on jruby has reportedly reached 14000 rps on similar hardware to what he's refering to (8 cores, since he previously claimed to get 5000 rps on a 4 core machine).
But it sounds like you were doing profiling and optimization early and often, which might have been premature, and thus might have been a waste of time.
Who's to say? Ruby isn't for everyone. Perhaps your ideal web stack is what you're using. (What're you using, btw?) I've been itching to use Haskell for a webapp.