> And the solution is going to be at least 10x slower than the java one. Even if that was true (there are many ways to make ruby/python faster), who cares? Har

> And the solution is going to be at least 10x slower than the java one. Even if that was true (there are many ways to make ruby/python faster), who cares? Hardware is like 1/100 of the cost of an engineer. Use more/better hardware, and problem solved. Optimize for your most expensive resource. Sure maybe 20 years ago that was processing time, but now in days your end user can't tell the difference. I mean does 10ms really feel any different from 100ms? Not really. (OK, there are some times when processing time DOES matter, but that's the exception, not the rule. No premature optimization please)