How to Clean Text Data at the Command Line

Re:How to Clean Text Data at the Command Line by hnlmorg on Tuesday October 20, 2020 @06:03AM (#24835631)

Don't be so ridiculous. You're the one imposing arbitrary problems by saying "everything should be written in awk" then writing an example that was an order of magnitude longer in both character count and execution time than the examples that you were suggesting was wrong.

All I'm doing is citing a few reasons why someone might prefer a terser pipeline but I hadn't realised this wasn't supposed to be an objective conversation and since I have no interest in engaging in pointless language fanboyism I'm just going to leave you to it.

[ Parent | on HN ]

Re:How to Clean Text Data at the Command Line by dredmorbius on Tuesday October 20, 2020 @09:39AM (#24837134)

"everything should be written in awk" is a rather dubious translation of:

a quick translation to straight awk gives cleaner code, more power, easier conversion to a script, and access to a small library of awk-based utilities I've acumulated.

https://news.ycombinator.com/item?id=24822697

You're not discussing what I've actually written.

Good day.

[ Parent | on HN ]

Re:How to Clean Text Data at the Command Line by hnlmorg on Thursday October 22, 2020 @06:35PM (#24864010)

I addressed those points directly, which you ignored when you blamed me of arguing use cases specific only to me. Suffice to say your complaint was hypocritical given your statement previous to that was very specific to your use case (as I also pointed out in my aforementioned, but ignored, comment)

[ Parent | on HN ]