Pat Eyler of O'Reilly's Ruby blog has interviewed James Gray of Ruby Quiz fame. James talks about how he was won over to Ruby via Perl 6, and how the Ruby Quiz has continued to explode in popularity.

Stefan Kaes takes a look at common performance problems with Ruby on Rails. He looks at:

From the ever-productive Erik Veenstra comes AllInOneRuby, a "Just-in-Time and Temporary Installation of Ruby". The concept is simple:

It's not the nicest code you'll ever see, but it's a great demonstration of the power inherent in Ruby on Rails. Miklos Hollender demonstrates how he created a version of Web 2.0 app, Reddit, in under 20 minutes using Rails, scaffolding, and a little elbow grease. Source is included.

A few days ago, Courtenay of Caboose posted an article called 'pretty tables for ruby objects' that give a MySQL-command-line-client style textual view of data stored in your Rails database. The syntax worked like this:

BackgrounDRb, by Ezra Zygmuntowicz, is a system that lets you run long running tasks in the background, and not in the scope of your application. For example, you might have a Rails application that needs to send 100 e-mails, but rather than tie it to an HTTP request, you can simply pass off the job to a BackgrounDRb object and let the user know everything is proceeding as planned. There's more information here.

Coda Hale is a Rails developer from Berkeley, CA, who's developed a ton of useful plugins. I'll leave the descriptions to Coda:

One of the features of Rails 1.1 was the ability to automatically detect clients that could understand XML and send XML responses to them using the respond_to method. This also works for AJAX requests and HTML, of course. Unfortunately, though, this relies on XML and API clients sending the correct Accept headers in most cases, and, as we all know, users aren't necessarily so smart (even API users!).

Paul Lutus says: