3 ms·
Yup, exactly. I think a big reason they never took off is also that there's no visual representation of them, or input method for them. I'd be happy to use th
by crazygringo 2y ago
Yup, exactly.
I think a big reason they never took off is also that there's no visual representation of them, or input method for them.
I'd be happy to use them instead of CSV if I could edit records in Notepad or TextEdit the way I can with commas and quoted strings. See the separators, type them.
But of course once you do that, somebody now wants to insert a list of five values separated by unit or record separators into a field. They'd just be common ASCII characters along with tab, CR, LF, etc, and need to be escaped the same.
There's no escaping escaping...
- indymike 2y agoThose characters were "control characters" and used for streaming data over serial, parallel and other devices. Control character could cause some real surprises when you used them. > There's no escaping escaping... This is the truth.
- Dylan16807 2y agoXML has gaps in its escaping. (Oops I wrote JSON at first, got the technicalities mixed up.) Null-terminated strings don't have escaping. Fixed width formats don't have escaping. Type-length-value formats don't have escaping. And in practice I do not expect CSV with embedded nulls to work properly, so there's already precedent to reject certain characters entirely in a CSV-like format.