2 ms·
Some of these look like broken CSV parsing. Which has been incessant across my 13+ yr career. Perhaps we can evolve from a 1970s tech to something less flaky?
by maerF0x0 4y ago
Some of these look like broken CSV parsing. Which has been incessant across my 13+ yr career.
Perhaps we can evolve from a 1970s tech to something less flaky?
- imiric 4y ago/shrug I like CSVs. Or, rather, TSVs. They're simple, structured and interoperable. It's the first format I reach for when building small pipelines. The fault is not with the format, but with the developers that choose to use it after they've outgrown it. For anything more complex, choose SQLite. For everything else, choose Postgres. Use the right tool for the job. There's likely much worse things happening in these cases than just broken CSV parsing. Since these issues got deployed to production, lack of testing, for one.
- maerF0x0 4y agothey're simple on the surface, until you get into the details of UTF BOMs cell escaping, handling jagged rows, and maybe a few other edges I'm failing to note right now