Long Rails Stack Trace
I was looking at the RailsConf schedule, and saw the Rails web app that runs it fail with this longish stack trace. A few Rubyists sitting nearby commented that the application was not well configured, that usually Rails apps are configured in deployment to store such traces to a log, rather than spit them at the user. Their mistake is my gain though, as it provided fodder for this post.
This stack trace is considerably shorter than a typical Java web app stack trace. But it is not so good either, and it is an ominous sign that excessive complexity is making its way in to Rails.
|
July 28th, 2006 at 11:01 am
Who are these mongrel ruby developers?…
After investigating an unusual stream of visitor referrals onto this blog, I stumbled across this. Here’s a quote:
… this wonderfully hilarious stack trace (and the comments to back it up). Somehow it doesn’t dawn on the author that his…