From: Nathan Ahmed Date: 2012-09-19T17:41:57+09:00 Subject: Re: Ruby - is it worth the effort? --e89a8fb20524a45f1a04ca09fa93 Content-Type: text/plain; charset=ISO-8859-1 That's what it comes down to ... right tool for right job. On Wed, Sep 19, 2012 at 4:36 PM, Peter Hickman < peterhickman386@googlemail.com> wrote: > On 19 September 2012 09:24, Robert Klemme > wrote: > > On Mon, Sep 17, 2012 at 8:20 PM, Peter Zotov > wrote: > >> That being said, I won't write number crunching algorithms in Ruby, or > work > >> with gigabyte-sized datasets. > > > > Well, even that depends. Sifting through logfiles of that volume is > > almost certainly IO bound and the processing speed can be negligible. > > That of course depends on the processing. > > Being a Ruby shop we try to use Ruby everywhere but when it does come > to grinding through logfiles (some several gigs in size) we had to go > with Perl. The string processing and regex matching was so much > faster. We couldn't get Ruby even close :( Speed was essential, we > couldn't just sit around and wait for the process to complete. > > Right tools for the job I guess. Ruby is fine for everything else so > switching it all over to Perl would not really gain us anything. > Besides if you are a programmer knowing more than one language is a > must. > > --e89a8fb20524a45f1a04ca09fa93 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That's what it comes down to ... right tool for right job.

On Wed, Sep 19, 2012 at 4:36 PM, Peter Hickman <peterhickman386@googlemail.com> wrote:
On 19 September 2012 09:24= , Robert Klemme <shortcutt= er@googlemail.com> wrote:
> On Mon, Sep 17, 2012 at 8:20 PM, Peter Zotov <whitequark@whitequark.org> wrote:
>> That being said, I won't write number = crunching algorithms in Ruby, or work
>> with gigabyte-sized datasets.
>
> Well, even that depends. =A0Sifting through logfiles of that volume is=
> almost certainly IO bound and the processing speed can be negligible.<= br> > That of course depends on the processing.

Being a Ruby shop we try to use Ruby everywhere but when it does come=
to grinding through logfiles (some several gigs in size) we had to go
with Perl. The string processing and regex matching was so much
faster. We couldn't get Ruby even close :( Speed was essential, we
couldn't just sit around and wait for the process to complete.

Right tools for the job I guess. Ruby is fine for everything else so
switching it all over to Perl would not really gain us anything.
Besides if you are a programmer knowing more than one language is a
must.


--e89a8fb20524a45f1a04ca09fa93--