[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ale] Bash vs Perl



> From: "leam hall" <leamhall at gmail.com>
> To: "Atlanta Linux Enthusiasts" <ale at ale.org>
> Sent: Monday, October 24, 2016 12:55:03 PM
> Subject: Re: [ale] Bash vs Perl

> I'm not sure I know a lot of Ruby either, but the logic is the same. Calling
> sub-programs is expensive in terms of minute measurements. Overall, if you fork
> 25 time in one day, what's the actual impact? If you fork 2500 times a second
> for several hours straight, then you probably want a compiled language.

I don't have a day to write, compile, test and deal with SIGSEGV in one day. I do have time to do it in Perl. In my example I'm trying to convert data or look for data in a large dataset. In the sqlite3 example with many rows I'm storing file attributes or a catalog of files in SQL format. I'uu fork and use find to feed me the file list and then I'll do everything else in on process. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20161024/291b9ea4/attachment.html>