Re:Cheating at a company group activity using Unix tools
by ccalloway on Monday December 13, 2021 @12:07PM
(#29541560)
Did you read or understand my original comment?
I specifically named awk as a way of solving these type of problems that has a similar applicability and maturity to a scripting language. My real objection is to long chains of cut, head, cat, grep, and so on. I also think that utilities like jq and xargs, which were invented exactly to allow people to do things in shell one-liners which are trivial in a proper language, are worse than useless.
I didn't say that no one should use awk, or no one should use the command line.
In fact I didn't say that no one should use pipes with head, cut and grep either. I just said that most reasons to use them were no longer valid.
To move stuff to that cattle and to maintain cloud environments, to prepare k8s clusters and manage those. To create docker images or to maintain servers that are running k8s.
You still have AWS console and Azure CLI or GCP console and configurations that need to be search/replaced. You still need to parse logs to understand what is happening in multiple environments, which I would say makes it even more important to be good with unix-fu because you have to find that one broken cow to put it out of misery.
Those command line tools are still useful and used.