Message-ID: <66c26fda@news.ausics.net>
From: not@telling.you.invalid (Computer Nerd Kev)
Subject: Re: AWK As A Major Systems Programming Language
Newsgroups: comp.misc
References: <slrnvc2fsg.gg1.bencollver@svadhyaya.localdomain> <awk-20240818120618@ram.dialup.fu-berlin.de>
User-Agent: tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586))
NNTP-Posting-Host: news.ausics.net
Date: 19 Aug 2024 08:04:11 +1000
Organization: Ausics - https://newsgroups.ausics.net
Lines: 22
X-Complaints: abuse@ausics.net
Path: ...!weretis.net!feeder9.news.weretis.net!news.bbs.nz!news.ausics.net!not-for-mail
Bytes: 1518

Stefan Ram <ram@zedat.fu-berlin.de> wrote:
>>I have worked for several years in Python. For string manipulation
>>and processing records, you still have to write all the manual stuff:
>>open the file, read lines in a loop, split them, etc. Awk does all
>>this stuff for me.
> 
>  On the flip side, you can peep it like this: Python's got a solid
>  set of statement types you can use for everything, making the code
>  hella readable. Meanwhile, awk's got its bag of tricks for special
>  cases like file and string processing. Just compare [1] with [2].
> 
>  [1]
[snip]

Weird, as someone who doesn't use much of Python or AWK, I look at
your examples as clearly demonstrating that the AWK version is much
easier to read. I wonder if the Python version is more complicated
than it needs to be actually.

-- 
__          __
#_ < |\| |< _#