> Rails remains the slowest and least efficient server side language by a huge margin.
Rails is a framework, not a language, and its not clear whether this "slowest server side <foo>" is really directed at Rails (the framework), Ruby (the language), MRI (the main implementation of the language), or some combination of framework, language, and implementation.
Yes, I should have said framework instead of language. However, MRI also happens to be one of the slowest languages. What are proposing as a good combination that people are using?
There is also Rubinius, and JRuby. Not to mention a few versions of threaded servers for each. Rubinius + Puma shows huge potential, I am running very large Rails app on a DigitalOcean 512MB ram droplet using it, and not using more than 30% memory.
The problem with your comment is while Javascript has improved and while Rails is still relatively slow, both Rails, Ruby implementations, AND server speed in general has gotten faster AND cheaper.
Not to mention the absolute ease of setting up russian-doll caching throughout with (distributed) memcached, and potential further speedups for all the interpreters (and the upcoming Topaz) and I'd say you presented a very one sided response.
Rails is a framework, not a language, and its not clear whether this "slowest server side <foo>" is really directed at Rails (the framework), Ruby (the language), MRI (the main implementation of the language), or some combination of framework, language, and implementation.