Years ago, when ASP was first taking off it wasn’t uncommon to discover errors when surfing the net.
Those first ASP apps seems to break so often, their little VB errors calling out to the wild.
Today I’ve been immersing myself back into Rails, and what have I discovered?
Rails sites seem to have the same affliction, three times today I’ve visited various ruby sites to be struck by variations on ‘Application error (Rails)’.
Now, if the measure of a community is how it eats its own dogfood then its great these guys are running Rails, but its a disturbing fact it seems to be so unreliable?
And now I await the flames 
April 15th, 2006 at 6:19 pm
I have a difficult time attributing this to the stability or instability of Rails. Quite often this is a user error caused by developers running on shared hosts who neglect to lock their Rails application to a particular version. When the Heinous Upgrade occurs, their app might not be ready. Lock your application.
That being said, there are certain caveats within Rails that are difficult to address. One of them is the framework’s reliance on PStore to persist session data, especially when PStore stores these session files in /tmp. Although this isn’t a hard and fast rule, PLANET ARGON prefers to use the ActiveRecord session store to persist session data in session-intensive applications. It takes roughly 5 minutes to implement this.
Finally, some of these errors will share the same cause as the class ASP or PHP errors - there is a genuine bug in the application code, a configuration error or a missing dependency.
It truly is frustrating for users to encounter these errors - especially if the user also happens to be a Rails developer - but simply attributing this to the framework seems to be a cop-out without bringing any hard evidence to the table.