What I imagine I will use Perl for is as a replacement for Sed, Awk, and all those little tools that are simple but either have annoying differences or are gimp

What I imagine I will use Perl for is as a replacement for Sed, Awk, and all those little tools that are simple but either have annoying differences or are gimped in some way or another. I don’t like SSHing into another “box” and being at the mercy of that things `PATH`, but if most of those boxes have Perl installed then at least I can bring some utility scripts with me. But beyond that? I think not. As an application programmer Perl will never be a daily tool for me. So it gets relegated to that once in a while toolshed. But then that Tim Toady slogan kind of might get in the way: I don’t want to google for all kinds of “creative” ways to just get from A to B. Because I will surely be in that annoyed, I just wanna get this thing done kind of mood (is “in anger” the right phrase?). > We can easily invoke a Perl daemon to avoid spending hours working on C and avoid several security flaws. > […] > In today’s event-loop-centric asynchronous world of JavaScript, node.js, and TypeScript, Perl offers a very straight-forward code flow, and Perl code offers simplicity and control. In a few paragraphs the author went from some ’90s looking argument (you don’t even have to touch C) to mentioning baby’s first exotic synchronous programming encounter. I almost got a whiplash.