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

[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.

On Mon, Oct 24, 2016 at 12:48 PM, Chris Fowler <cfowler at outpostsentinel.com>
wrote:

>
>
> ------------------------------
>
> *From: *"leam hall" <leamhall at gmail.com>
> *To: *"Atlanta Linux Enthusiasts" <ale at ale.org>
> *Sent: *Monday, October 24, 2016 12:08:48 PM
> *Subject: *Re: [ale] Bash vs Perl
>
> My unsolicited opinion, based off using Ruby, is that if the cost of a
> fork is critical use C or Go. Otherwise, "a difference that makes no
> difference is no difference".
>
>
> I don't know Ruby, but I'm sure you can text processing without executing
> awk, cut, sed, tr, and their other friends.   I'm talking about the expense
> when you need to do processing that would require call those programs.
> The annoyances of those friends is the subject of another day. :)
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>


-- 
Mind on a Mission <http://leamhall.blogspot.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20161024/12fc4c2a/attachment.html>