From: Devin Mullins <twifkak@...>
Date: 2006-01-04T12:58:59+09:00
Subject: Re: application and web app technologies

ccc wrote:

>Exactly! And a major decision is deciding on a technology so that we'll
>all be using the same thing.
>  
>
If I had to pick a technology to unify in a development shop, it'd be 
the source code repository. More important, though, is unifying the 
version/build process.

>Actually, Java was a pretty easy decision to make, since we already had
>a problem with Perl, no one wanted to do C or C++, and no one knows VB,
>and most of us had used Java at some point along the way. HOWEVER, we
>know we face a learning curve, and we want to get the most bang for the
>buck, and we have a good enough handle on our Perl scripts so this
>isn't a time critical desicion, so we are just looking.
>  
>
Try Ruby. It's friendly for Perl users, but object-oriented enough to be 
competitive with Java (which, granted, isn't saying much). 
http://tryruby.hobix.com/

Of course, this is a Ruby mailing list, so don't expect lack of bias...

I do agree with everyone else, though, that your solution may best be 
acquired in a non-technical way first. Once you've found that your 
process is improving, and you're able to track changes, and whatnot, 
*then* you can look around for new toys -- er, technologies -- to play with.

Devin