Bon, vu que je suis malade, autant troller.

Comme 99% de la planète, j'en ai un peu rien à foutre de Twitter et je me demande pourquoi tout le monde en parle, mais cette interview d'un des développeurs est marrante, c'est un fan de ruby qui tape sur ruby:

The common wisdom in the Rails community at this time is that scaling Rails is a matter of cost: just throw more CPUs at it. The problem is that more instances of Rails (running as part of a Mongrel cluster, in our case) means more requests to your database. At this point in time there's no facility in Rails to talk to more than one database at a time.

(..)

All the convenience methods and syntactical sugar that makes Rails such a pleasure for coders ends up being absolutely punishing, performance-wise. Once you hit a certain threshold of traffic, either you need to strip out all the costly neat stuff that Rails does for you (RJS, ActiveRecord, ActiveSupport, etc.) or move the slow parts of your application out of Rails, or both.

(..)

It's also worth mentioning that there shouldn't be doubt in anybody's mind at this point that Ruby itself is slow.

(..)

If you're looking to deploy a big web application and you're language-agnostic, realize that the same operation in Ruby will take less time in Python.

Bon voila, je peux retourner me coucher.