🚀 go-pugleaf

I'll demonstrate my bozo nature, and follow up...

Perl!=gawk!=nawk!=awk!=(POSIX awk). If you want to use perl, use
perl. If you want to use gawk, use gawk. If you want to use
nawk, use nawk...

It seems like Tom is trying to say "gee, Perl does all this, just use
Perl, and forget about enhancing gawk". Many folks don't like Perl,
because of confused syntax trying to look like TECO or other bizarre
feeps, so that's not necessarily a terribly helpful or useful
suggestion.

I don't like the idea of adding every bug/feature in the known
universe to gawk either, but rather than suggest "use Perl" I'll
suggest thinking about what gawk is good at and improving those
features, instead of trying to add lots of useless and obscure feeps
in order to turn it into a sploding mass of seeting putrid
obscenities.

Yes, people will write code for "gawk". Yes, people write code for
"gcc", "g++", and "bash" too. It sucks, but you can't force people to
write portable code. That doesn't mean that one shouldn't add new
features to programming languages either, or that two shouldn't use
them. Three, I say. Four.
						Bob