From the Rails weblog and in the latest volley in the continuing saga of Rails vs. Everyone Else, DHH proclaims, “the other consultancy bid a million dollars for a Java-based system, but the CIO picked the Rails solution.”
Instead of Java, they differentiate themselves by pitching a Ruby on Rails solution. Quite innocently, they undercut their competition by pricing their bid at $800K and promising delivery within 6 months. According to their calculations, (and once again, these are rough figures), 4 resources x $192 rate x 8 months equals about $800k.
Obie also cites another pair of articles with a particular Relevance: Ruby/Rails—Put your money where your mouth is and its successor, Bidding Projects with Ruby/Rails, Take 2. Coming from the blog of some Java heavyweights, this is great stuff. A couple of choice cuts,
For the past 18 months, we have been quietly bidding web projects with both Java and Ruby on Rails. The numbers for us, so far, fall out like this: for applications in the Rails sweet spot (CRUD+Ajax on the web) our Rails price tends to be 30-50% less than the same bid implemented in Java.
And on the topic of maintainability,
One thing I point out to customers is that maintenance cost is some function of the size and quality of the codebase. A well-written Ruby codebase can be an order of magnitude smaller than a similar codebase in Java.
Maintainability is a combination of several factors. Most important is: can you read and understand the code? Ruby on Rails wins in this category because it’s brief – smaller and thus easier to comprehend than Java – without being cryptic like APL. Second most important is: is it easily modified? Here Rails wins again, because of the say it only once philosophy and because of Ruby’s duck typing.
All this on the very day that 37signals opens the doors of speculation on their newest product, Sunrise CRM.