That assumes that the tools maximize human capital more than the tools that maximize both human capital and minimize server cost. Do they?
I don't know what you mean by reducing moving parts. The only parts involved in handling the requests for this setup are Nginx and HAProxy. All the other technology parts (Tokyo Cabinet, memcached, Sphinx) are used to scale the database, something your stack still has to achieve.
Lucene, ehcache -- in-process libraries to achieve the same effect but without all the moving parts. Or, instead of lucene, PostgreSQL's built-in FTS.
You also don't need nginx, haproxy, and a complex architectural division between static/non-static content.
The tradeoffs between using bare metal vs VM and using Rails vs Java are well known at this point.
I'm not sure I agree, given the constant repetition of "Ruby is more productive" as a justification for poor performance and complex architecture. Is it more productive than Scala? Clojure? Groovy? What about using even just using JRuby?