This post originated from an RSS feed registered with Ruby Buzz
by David Heinemeier Hansson.
Original Post: Ruby FAQ and RCRchive are put on Rails
Feed Title: Loud Thinking
Feed URL: http://feeds.feedburner.com/LoudThinking
Feed Description: All about the full-stack, web-framework Rails for Ruby and on putting it to good effect with Basecamp
David A. Black has just finished converting not one but two of the stable Ruby community sites to Rails. The Ruby FAQ is a searchable archive of questions and answers on all things Ruby. It was originally written in Iowa by Dave Thomas long, long ago, but due to lack of maintenance it was in bad shape and ripe for a rewrite. Enter Rails.
The RCRchive is a database for Ruby Change Requests. That is if you'd like something to change in the Ruby language, you write an RCR and the community comments. If enough people like it, Matz will have a look and a final word on whether it will go in or not. This system is now also powered by Rails.
If that wasn't enough for Mr. Black, he has also started developing the Aside application that he presented thoughts (PDF) on at RubyConf '03 in Rails. I believe it's scheduled for a demo at Seton Hall University — where David is an Associate Professor of Communication — later this month.
To top it of, RubyGarden has a new article online called Reflections on Rails where David gives his opinion on developing with Rails. Here's a taste:
It’s actually very similar, in its domain, to the feeling many get from Ruby itself. For me, it also represents a kind of enforced de-spaghettification that can only be for the good. Yes, one can write spaghetti code in a Rails controller. But the organization of one’s project itself will militate against it.
Oh yearh, David hadn't touched Rails — or any web-framework for that matter — before RubyConf '04 (which he organized with Chad Fowler and others). So all of this Rails activity has happened within the last three weeks or so. Now I'm the one impressed.
Previous Topic
