From: James Britt <james_b@...>
Date: 2005-06-04T06:00:13+09:00
Subject: Re: Building a business case for Ruby

Joe Van Dyk wrote:
> Hi,
> 
> I asked this question a little bit ago, but wanted to bring it back up.
> 
> I work for <insert huge company that makes really big expensive things
> here>.  We have "computing standards" that define what's allowable for
> usage internally and externally.  Technology evaluation boards, etc.
> 
> Here's an evaluation of Ruby:
> 
> "XXXX already has Product Standards for Python and Perl as
> Scripting/Dynamic languages. And for Java as a full programming
> language.


Mmmm.  Bias.  Not good.
> 
> Ruby offer nothing significant not found in these XXXXX Standard
> languages, and an addition language just adds variation."
> 
> Boo, I say!  Boo!


Boo, perhaps, but try turning this around.  Suppose Ruby, not Python, 
were already on The List, and someone comes to you to make a case for 
adding Python.

What do want to hear to convince you?  What are you tossing back when 
told of Zope, or Twister, or the extensive Python XML tools, or the 
amount of documentation, or how it's a great beginners' language, or 
whatever Pythonistas think makes a compelling case?


> 
> We've got mountains of unmaintainable perl stuff here, and I haven't
> really seen much in Python.  I'm in charge of developing some new
> software and would like to use Ruby.  Actually, the software is
> finished (very quickly) and I just need to get Ruby on the allowed
> list.  :(

Isn't this, then, the best argument?  Use Ruby and have code finished 
yesterday, or use P* and either never really finish, or never really start?

> 
> I don't need arguments about Perl vs Python vs Ruby.  I would like to
> see a discussion of:
> 
> 1)  Why one additional language isn't a bad thing

But it is, all things being equal.  It just adds complexity and risk, 
unless the new language has a compelling use-case.

I would argue that, if indeed there is little to no Python, that Ruby 
should be added *in place of* Python.  (This works especially well if
there are no Python developers to argue back.)

You'll need to present a money case; if adding Ruby means making more 
money, or saving more money, or both, then you're (probably) golden.

James

-- 

http://www.ruby-doc.org - The Ruby Documentation Site
http://www.rubyxml.com  - News, Articles, and Listings for Ruby & XML
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com  - Playing with Better Toys