[jamal-kumar]

AWK is sweet for big/streaming data analysis operations because by default awk/sed handle data without allocating memory. They're still highly used in these use cases just because it's typically easier to munge a gargantuan CSV file using command line tools that zip fast as fuck through it to get to the data. These tools come from days when malloc wasn't just an expensive bottleneck computationally, but expensive in terms of like 32MB of RAM or way less. If I need an application to get to data that huge (And there is PLENTY OF IT and more to come in these days, so it's pretty dope and groovy that this tool from the 70s is one of my best friends still -- care for your elders), I will get all modern or whatever and write one in go.