Oooh! AWK is usually my go-to language for almost everything!
Mind you, "almost everything" I do involves processing long lists of text: log files, address books with tens of thousands of contacts, all election candidates in the whole region... so AWK is usually the correct choice. But even when it's not, I usually start with AWK anyway.
@bobjonkman I am really good with cut, sed, and a bunch of other shell tools - meaning I never really ending up needing awk - but there's a bunch of places where you need awk
Wow! An entire #HackerPublicRadio series on #AWK. I'm sure I've heard some of these already, but I'll see if I can add just the series to @AntennaPod and decrease even more my copious amounts of free time for listening 😉
And, of course, repeat my so-far unkept promise to contribute an episode or two. I hear @hpr is running low on episodes again.
@bobjonkman@ghostdancer@AntennaPod@hpr@silverwizard In my case discovering #AWK was an introduction to the "Unix Way". I found a version to run on the OpenVMS system I was administering in the 1980's or later, and it made life so much easier. Handling data from the student records system (to make accounts for them) was so much easier than writing compiled programs!
@perloid@ghostdancer@hpr@AntennaPod@bobjonkman AWK always feels like an arcane thing to me - it's something my dad has implemented three times on three systems - and so it's kinda always been a mythical tool. But so has KornShell and that's also my default shell.
@silverwizard@perloid@ghostdancer@hpr@AntennaPod@bobjonkman I used awk in my hardware detection script, but I had to look up how to use it and then experiment a bit... Sed and awk are both a bit mystical to us 'desktop users.' :) But still super handy for hacking together things.