> I think it's completely my fault for not articulating myself properly, thank you for your patience. Not at all, and thank you for your patience and engaging

> I think it's completely my fault for not articulating myself properly, thank you for your patience. Not at all, and thank you for your patience and engaging this deep! I think the disagreement came from different people. I initially tried to question why /u/guidedlight thought a certain delimiter would be easier/simpler just because it was less common and then we went down a rabbit hole of "what is a CSV/TSV". I agree with you and I think there are many use-cases for not-as-full CSV/TSV parsers/encoders. My main objection was calling a CSV/TSV implementation a CSV/TSV implementation when it clearly skipped a lot of parts (while it can of course parse a lot of files without those parts). I'd like to call those simpler formats something other than CSV/TSV, but that ship has sailed. So I think it seems like we are on the same page.