There was a bit of a kerfuffle in the tech end of the blogosphere today about the possibility of the RoR posterchild Twitter giving up rails and re-implementing in Java. That in and of itself isn't that surprising. The 'sphere is currently atwitter (ahem) about load and scaling, what with the release of AppEngine et al.

No, the funny bit is that apparently Twitter have published a statement that they aren't giving up on Ruby on Rails. And on the other side of the link? A broken 500 Server Error page. That's just priceless guys...