4 ms·
I like the format description, thanks. Sounds like something I might implement some day for fun! The reason I still don't like this is because most of the time
by gnulinux 4y ago
I like the format description, thanks. Sounds like something I might implement some day for fun!
The reason I still don't like this is because most of the time I'm sharing csv is to a jira ticket or an email, or to customer and customer insists it needs to be csv.
When customer wants csv there is nothing I can do.
But in other cases I see this CSV file. So it's visual clarity is important. CSV has all the problems you listed, but TSV (and similar, such as your format) has the short coming of relying on an invisible separator. And worse, the width of tab is undefined, undecided.
I don't know what the best trade-of... Maybe we need better tooling so frontends show CSV/TSV et al as separated by cells.
- marcosdumay 4y agoWhen the customer wants csv, it's because they will open it on Excel, so anything about standardization or data quality is moot. They will have their data mangled in an application specific format. You need to export to csv. But that doesn't mean you can't use an actually usable format for anything else.