Thanks for this - but its the age-old argument of dynamic language vs static/compiled language mixed with hey bloated libraries! and hey bloated features! etc.

0. Performance isn't everything, especially to a lot of companies where having something at all is more important than just being the fastest

1. Dynamic languages are generally require less LOC, which generally equates to faster implementations

2. Rails, Django, <your favorite dynamic language framework> sure are generally bloated, but being able to drop in a library for nearly anything you need cannot be overlooked. Especially for small-midsize companies, spinning up another app server is generally easier than writing a whole bunch of multi-threaded code.

3. The appserver is generally not the bottleneck, rather, of course, its the database.