Back when Perl was the language of choice for bioinformatics, I found a huge performance boost pre-processing large (~1Tb) text files using built in unix tools like sed and awk with regex. So while it might take me a full hour to peck out the correct incantation, the task would then run in an hour, compared to four hours or more for the same task using Perl.
I play with it sometimes, kinde like some of the syntax, especially regex and ;.
I tried doing regex with sed when working on one personal script, but was getting errors way too often everywhere. Perl did what I wanted in a few lines and gave me desired output, so I just used that.
Imo, it doesn’t really matter what you use for writing code for your personal use as long as it works.: )
I’d sooner pipe a dozen POSIX commands together than write a single line of Perl.
Back when Perl was the language of choice for bioinformatics, I found a huge performance boost pre-processing large (~1Tb) text files using built in unix tools like sed and awk with regex. So while it might take me a full hour to peck out the correct incantation, the task would then run in an hour, compared to four hours or more for the same task using Perl.
So many pipes…
The beauty of Unix philosophy
A program does one thing, and it does it well
@davel @learnbyexample
Too bad. You are missing out on a great language.
I walked away from Perl about a decade ago, after having used it for about a decade. I have not missed it.
I play with it sometimes, kinde like some of the syntax, especially regex and
;. I tried doing regex withsedwhen working on one personal script, but was getting errors way too often everywhere. Perl did what I wanted in a few lines and gave me desired output, so I just used that.Imo, it doesn’t really matter what you use for writing code for your personal use as long as it works. : )