3 ms·
NSVs break any text-based tools e.g. not only is it hard to view them using standard tooling, you can't diff them either. And if you're going to use stupid sep
by masklinn 6y ago
NSVs break any text-based tools e.g. not only is it hard to view them using standard tooling, you can't diff them either.
And if you're going to use stupid separators, at least use US (0x1F), that's the entire point of that thing.
- fctorial 6y agohttps://prnt.sc/vf7699 https://prnt.sc/vf7699 This is how vim renders an NSV file. And I honestly don't remember the last time I edited a csv file by hand.
- Kwpolska 6y agoAnd this is how TextEdit does it: abc 123 CSV files are also editable and readable with basic GUI tools like TextEdit/Notepad. Users of CSV files are not just people who can use Vim or a hex editor, it’s a general-purpose format. I can’t read nor edit the file with TextEdit, Notepad might also make it hard. Software that assumes C-style strings (where NULL terminates a string) can’t process your file without a complete rewrite. And even with Vim, I had to type ^Vu0000 to get the NULL in there, which is much less comfortable than comma or tab. (No, I’m not adding a key sequence for NULL to my .vimrc.)