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
this post was submitted on 01 Jul 2025
19 points (100.0% liked)
Programming
21357 readers
305 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
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
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.
We want to move down to the next line (line feed) but also to the beginning of that line (carriage return) after all.
I hate that the pleasant news about standardization of CSV come with the let-down that is using two bytes for new lines.
Don't worry, it's not really standardised despite this attempt. You can use UNIX line endings and nothing bad will happen.
Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
If I am using Excel, I am using Windows and I will be changing all text to use CR-LF newline format (if sending from a Linux system) anyway.