----------------------------------------------------------------------------------
@MSGID: 1@dont-email.me> 2e681400
@REPLY: 1@news.xmission.com>
4b61aa1a
@REPLYADDR Muttley@dastardlyhq.com
@REPLYTO 2:5075/128 Muttley
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID: 1@dont-email.me>
@RFC-References: <kmj8hhFq8tqU1@mid.individual.net>
1@dont-email.me> 1@dont-email.me> 2@dont-email.me>
1@news.xmission.com>
@TZUTC: -0000
@TID: FIDOGATE-5.12-ge4e8b94
On Sat, 16 Sep 2023 17:27:09 -0000 (UTC)
gazelle@shell.xmission.com (Kenny McCormack) wrote:
>In article
2@dont-email.me>,
>candycanearter07 <no@thanks.net> wrote:
>>On 9/16/23 03:58, Muttley@dastardlyhq.com wrote:
>>> Seems to me far too many people try and use shell script way beyond what it
>>> was intended to do - ie navitage the file system, link commands together and
>
>>> job control - and use it where they`d be far better off simply using perl or
>
>>> python (or even awk) which leads shell authors to bung in features no sane
>>> person in their right mind would ever need, never mind use.
>>>
>>
>>I agree, being so simple and being *right there* draws in beginners who
>>don`t know other languages I think.
>
>Poppycock.
>
>I especially love the phrase (quoted above): simply using perl or python
>
>Yeah, right...
If writing code in scripting languages like perl or python is beyond you then
I would suggest you steer clear of any kind of programming and leave it to
people who know what they`re doing. People who couldn`t hack their way out
of a wet paper bag yet think they can write code in shell explains a lot
of the crap I`ve seen over the years written by sysadmins.
--- FIDOGATE 5.12-ge4e8b94
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441