"It's 2011, time for a sed v. awk religious war!"
Awk wasn't invented for lack of those things, Awk was invented to supplement those things. And for that purpose it is every bit as relevant today as it ever was.
P.S. Properly formatted, that awk line is perfectly sensible. I don't see what your issue here is.
When I 'grep awk /usr/bin/*' then I see only two types of usages.
Most commonly it's used in place of grep, sed or cut for no obvious reason. Gladly less common but all the more annoying is when someone tries to go all "fancy" with it...
It could be clearer without the variable-name golfing and as a seperate .awk file (instead of a CLI one-liner) but it reads pretty much the same as C without any pesky type declarations.
Awk is Turing-complete.
For any sort of script thats going to be run many times and may need to be improved or extended, readability is a huge plus.
Anything that doesn't fit into 80 chars that way is usually a sure sign that it's time to reach for a real scripting language rather than brewing up one of those line-noise blobs.
Oh, and of course I don't mind when people use it on their shell-prompt.
I do mind when I run into crap like this in a shell-script: