4 ms·
Except when you want to be sure you get what they intended. If it’s just some little throwaway project and you don’t care if the results don’t match up, use csv
by tinus_hn 4y ago
Except when you want to be sure you get what they intended. If it’s just some little throwaway project and you don’t care if the results don’t match up, use csv.
- bayesian_horse 4y agoThat'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.
- chasd00 4y agoit's mainly because excel can read csv ootb (mostly). Also, many old UNIX programs read csv or fixed-width for batch record processing.
- tinus_hn 4y agoYeah 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.
- bayesian_horse 4y agoExcel is much like an Incel: it has a tendency to mistake something for a date that isn't.
- RobinL 4y agoI would generally recommend parquet for the reasons set out here: https://www.robinlinacre.com/parquet_api/ https://www.robinlinacre.com/parquet_api/