Hacker News new | past | comments | ask | show | jobs | submit login

That's actually when I'd rather use something like pickle or feather, maybe even json depending on the usecase, which is easier to parse back.

I've encountered CSV mostly for data transfer among different programs. There sometimes are better options. Sometimes there isn't, maybe even just because CSV is easier and cheaper to implement on both (or multiple) ends.




Yeah as long as you don’t mind Excel changing a few values here and there and pretend translation and internationalization doesn’t exist. But hey, that’s ‘good enough’ so the developers don’t need to bother using a format developed in this century.


Excel is much like an Incel: it has a tendency to mistake something for a date that isn't.


I would generally recommend parquet for the reasons set out here: https://www.robinlinacre.com/parquet_api/


it's mainly because excel can read csv ootb (mostly). Also, many old UNIX programs read csv or fixed-width for batch record processing.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: