Now, on the funny side… Ruby is being developed in Japan and historically has been having issues with Unicode that is designed to solve problems with non-English locales.

John Adams, “Fixing Twitter: Improving the Performance and Scalability…”

http://velocityconference.blip.tv/file/2300327/

Anyone using RoR is foolish. Anyone sensible from that community bailed long ago. Funny you mention the disinterest of the basecamp guys, since they are “the” RoR guys. They mainly care about cash and ego.

Last bit of advice, techcrunch, you should bail on your RoR systems, future fail comming for you.

Care to explain why, after being informed 8+ hours ago that your last paragraph is completely factually incorrect, and seeming to acknowledge that fact, the piece still stands uncorrected? That’s absolutely insane. The Rails security release doesn’t even remotely say what you claim it does; simple reading comprehension would have disclosed that.

RoR is widely adopted, both commercially and non-commercially, tested by many people in many circumstances, and provides security comparable with any other web framework, and substantially more security than the default ‘no framework’ option. It has flaws, just like the rest of the stack will have flaws, but fixing them is the responsibility of whoever maintains that level of the stack, not the people who use it.

Thousands of people use off-the-shelf identikit Wordpress installs and noone ever complains, yet someone goes off on their own to code their own site+application using a base framework that merely undertakes the most menial of tasks, and you complain that they’re not “real developers”.
Why reinvent the wheel?

I also *highly* doubt that a single developer or small development team would be able to code something more secure that RoR first time (unless they were actively focusing on the security issue).
Every platform has security issues, we can only ever delay hackers, never stop them.

This is an interview to the Twitter team
http://www.artima.com/scalazine/articles/twitter_on_scala.html

Quoting from that article: “We find Ruby and Scala are very complementary. We use Ruby, actually specifically Rails, for things that it is very strong at. All the front end stuff that it does very well. [...] our plan for the long run is to move more and more of our architecture into Scala. The vast majority of our traffic is API requests, and we want most of those to be served by Scala, either at an edge cache layer or a web application layer. Hopefully by the end of 2009 the majority of users’ interactions with Twitter are going to be Scala-powered. ”

Don’t know at which point they are now but it seems to me that the front end (that is, the HTML pages) will be served by Ruby on Rails for the time being.