Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

it's better at reading UTF8 CSV files than Excel, too.


There is probably nothing that can read CSVs that does it worse than Excel.


An internal tool I'm responsible for maintaining (that coworkers at my company use) consumes CSVs, and a lot of the time they're made by less-technical employees who use Excel to create/edit them. Very often Excel causes unexpected bugs that baffle me when the tool can't parse it. One time it surprised me when all the cells looked right in Excel itself, but when I popped it into Emacs, there were ~15 extra commas at the end of every row. Don't know what world that would be expected behaviour in, but alright.


Extra commas mean extra cells. There are probably cells to the right of the data that are empty, but have formatting or something so that Excel thinks they are part of what needs to be saved.


Probably, but why would I want to keep formatted blank cells in my CSV data, when it doesn't even represent the style/formatting in any way? If there was any data I'd care about from those cells, it'd only maybe be the styling. But if it's not going to export the styling information, and the content is blank, then don't export those cells.


I don't understand why is so bad. If you use the insert data from file it ask you to choose separator and all that, great works fine.

If I open the CSV directly it doesn't and unless the files follows your system settings for separator and date a d similar it opens it wrong.


=cmd|' /C calc'!A0




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

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

Search: