4 ms·
Everything you just described seems like reasons to not use CSV files in general, rather than not use AWK on CSV.
by necheffa 6y ago
Everything you just described seems like reasons to not use CSV files in general, rather than not use AWK on CSV.
- sidpatil 6y agoI'm disappointed we didn't use ASCII-separated values. https://news.ycombinator.com/item?id=7474600 https://news.ycombinator.com/item?id=7474600
- nmz 6y agoAnd apparently an even better solution is just putting the size in the format itself. No need to parse when you can just seek. https://blog.kowalczyk.info/article/fc9203f7c72a4532b1ae51d018fef7b3/trade-offs-in-designing-versatile-log-format.html https://blog.kowalczyk.info/article/fc9203f7c72a4532b1ae51d0...
- protomyth 6y agoDid it multiple times and it works great, but companies you send raw data to often get huffy. So, back it goes into CSV or some poorly defined fixed width text file.
- im3w1l 6y agoI don't see what issue they solve. You still need escaping, because eventually you will want to put an ascii-separated value into your spreadsheet.
- smallnamespace 6y agoCSV is the default interchange in many fields (e.g. a lot of machine learning or academia). You don't get to choose what formats your colleagues send to you.