Jared's Weblog

Main Page - Books - Links - Resources - About - Contact Me - RSS

Jared Richardson Most Popular
Help! I've Inherited Legacy Code
Testing Untestable Code
Continuous Integration... Why Bother?
Mock Client Testing
The Art of Work
Technical Idiot Savants
Targetted Skills Aquition vs Free Range Chickens
The Habits of Highly Effective Developers

Blog Archive

Thu, 16 Feb 2006

The Rails debate makes Digg

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

posted at: 23:27 | path: | permanent link to this entry

A Rails Configuration Bug: How Ironic!

I started tinkering with Rails again and ran into a problem getting the Rails app talking to the database. I was copying DHH's blog video, so I was sure the Rails code was okay.

I tinkered with the setup long enough to get frustrated, upgrade MySql, add users, etc.

Then, turning to Google for the third or fourth round of searches, I found a gem. This blog entry.

It solved my problem. Which was only fair, since I'm the Jared mentioned in the post as providing the same answer last summer. :) What can I say? That was August. It's February. I've slept since then.

So, to the Rails team... I'm sure this "just works" on your Macs, and I'm getting one soon, but shouldn't the defaults be correct on the most prevalent operating system on the planet? Shouldn't the convention take over if the configuration is absent?

Add the port number to the database.yml file! Please!

Actually, I supposed I should find a page on the Rails web site and see if I can report the problem first... (this page looks like a good starting point) but I wonder how many people gave up after trying to get the database working with Rails after fifteen minutes and didn't discover the gem that is Rails?


posted at: 00:35 | path: | permanent link to this entry