I am assuming there really is a standardized format that uses tabs? Or do you just see it as intuitive to replace the commas with tabs? I’m really curious. I haven’t typically worked with huge datasets but when I’ve worked with exported/transitional data stored in files it is normally either a json or a csv (or a mysql export).
Would you want time to be saved as the 1/1000000 of a moon cycle since the last celestial alignment?
Or rather, would you care it it’s visualised as Christian based time?
I don’t get the joke… ?
I am assuming there really is a standardized format that uses tabs? Or do you just see it as intuitive to replace the commas with tabs? I’m really curious. I haven’t typically worked with huge datasets but when I’ve worked with exported/transitional data stored in files it is normally either a json or a csv (or a mysql export).
Bit of a joke related to bringing “what is TSV” to an “intense” TSV vs CSV debate.
As for TSV itself, it’s a widely used standard from 32 years ago, and is often a default record delimiter when used with GNU/POSIX tools.
It mostly exists as legacy at this point, as people now prefer quoted values like those given in CSV (ver2) and JSON formats.
Also most of (continental) Europe uses semi-colon delimiter, because comma is decimal separator.
I hate this so much, decimal localisation should be visually represented and saved with decimal points.
It’s only decimal “point” in English though.
Would you want time to be saved as the 1/1000000 of a moon cycle since the last celestial alignment? Or rather, would you care it it’s visualised as Christian based time?
ch-christian time…? that other one sounds insane
Ah, ok. Thanks for this response!