From: Robert Nesius <nesius@...>
Date: 2004-09-01T00:57:35+09:00
Subject: Re: Ruby for system administration


On Aug 31, 2004, at 2:40 AM, Martin DeMello wrote:

> I was talking to a sysadmin friend, who was shopping around for a
> scripting language. Naturally, I suggested ruby, and we spent a few
> minutes exploring its features, but it failed his crucial requirement -
> an interface to the package manager that shipped by default with the
> system ruby distribution. i.e., ruby on RedHatshould come with a ruby
> interface to the rpm db, etc.
>
> It seemed like a very sensible idea to me - what do people think?
>
> martin
>
>
Now that I've read the rest of the thread and added a few comments, I'd
say if your friend is the only person responsible for his box(s) no big
deal.  But if he is part of a larger team, and he is the only ruby
scripter around, he should not use ruby at all.  Because after he's 
gone,
it is going to be difficult for anyone to fix/change/maintain his code.
He should use whatever the group uses, and in most places that is perl.

Heretic, I know. :)  The point is he works in a group and other people
will have to maintain his code after he's moved on to other groups or
duties within his group, if he's the only ruby scripter, he's causing
a problem.  If he's the only ruby scripter but he's going to train
his colleagues on how to write/maintain ruby, that's ok then.


-Rob