I equate the statement that "throw hardware at the problem" in the case of Rails to be uneducated. The whole myth that Rails doesn't scale is becoming annoying.

I equate the statement that "throw hardware at the problem" in the case of Rails to be uneducated. The whole myth that Rails doesn't scale is becoming annoying. The video explains that it's not a framework or language that doesn't scale - it's either CPU bound or IO bound. Saying that Rails quates to 'throwing hardware' at a problem is silly because there are waaaaay more variables and once you get to the bottom of the problem you'll see that the framework makes little difference. In our case (soocial.com) we use rails for our webapp and ruby for most syncing bots - the bottle neck has been the database and never really rails. And we don't expect it to be.