January 17, 2006

Posted by John

Older: Tutorial on distributing Rails apps

Newer: The how and why of Rails unit testing

Answers for the Rails skeptics

J. Wade Winningham [has some answers for those skeptics](http://www.updrift.com/article/questions-ruby-on-rails-skeptics-ask) who don’t believe Ruby on Rails is up to the task, or that it’s too hard to use.

> If you have been following anything related to web development at all, you have at least heard of Ruby On Rails. If you’re like me, it makes you want to take a flying leap into developing with it. For personal projects there’s nothing to hold you back. However, if you decide to recommend using Rails with a team that doesn’t know much about it, you may run into some questions. If you don’t have some ready answers, the idea will most likely be shot down quickly and left in the dust.

What follows is a point by point renunciation of some common misconceptions about Rails, such as:

  • I don’t like using ‘id’ as my primary key name
  • Rails generates too much database server traffic
  • It’s difficult to find hosting

[Read his full post](http://www.updrift.com/article/questions-ruby-on-rails-skeptics-ask) for more.


Thoughts? Do Tell...

textile enabled, preview above, please be nice
use <pre><code class="ruby"></code></pre> for code blocks


Authored by John Nunemaker (Noo-neh-maker), a programmer who has fallen deeply in love with Ruby. Learn More.


Release your software more often with fewer problems.
Flip your features.