This post originated from an RSS feed registered with Agile Buzz by Jared Richardson. Original Post: The Rails debate makes Digg Feed Title: Jared's Weblog Feed URL: http://www.jaredrichardson.net/blog/index.rss Feed Description: Jared's weblog. The web site was created after the launch of the book "Ship It!" and discusses issues from Continuous Integration to web hosting providers. Latest Agile Buzz Posts Latest Agile Buzz Posts by Jared Richardson Latest Posts From Jared's Weblog

There were two great posts on Digg today. One talked about all the problems with Rails and why it wasn't so great. The second post walked through the critique and answered it point by point.

First, it's a good indicator for Rails that both posts made the Digg front page in a single day. Since it's a user voting system, the topic has to be popular to get that kind of traction.

Second, an old proverb says "Always listen to your enemies. They'll tell you things your friends never would." I think having a flat out listing of problems (or failed expectations or misunderstandings or ..) is great. If no one complains loudly, the problems can't be fixed or avoided. Maybe the user's expectations can be changed.

This type of public "discussion" is good for Rails and, more importantly, it's good for us. It helps us to know the system a little better, both the good and the bad.

Anyway, here are the two links.

First the bad: Rails' Ridiculous Restrictions, a Rant (posted anonymously).

Second, the response: Regarding Rails Restrictions (signed)

Read them both. Think for yourselves. See if you can find something about Rails that you didn't know before.

Enjoy! Jared