Programming

21981 readers

338 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

TIL that RFC 4180 specifies the CSV format to use CRLF line endings (datatracker.ietf.org)

submitted 1 month ago by JackbyDev@programming.dev to c/programming@programming.dev

7 comments fedilink hide all child comments

I noticed a repository's .gitattributes entry for *.csv used text eol=crlf so I investigated and found this.

you are viewing a single comment's thread
view the rest of the comments

[–] Laser@feddit.org 6 points 1 month ago (1 children)

I think csv is a bad format, if you can even call it that. Yes, there are some cases where it makes sense. I worked with an oscilloscope at uni which output csv. But other than that, I consider it more of a concept than an interface / exchange standard

[–] ulterno@programming.dev 3 points 1 month ago

more of a concept

And it's better to be considered so.
The name itself suggests a Comma as a separator, but we know how inconvenient that is and that tab characters tend to be useful in most cases.
Even LibreOffice Calc asks the user what they expect as the separator when given a csv file, even if it has enough commas to feel correct.