Surely the successor should be SQLite. Tabular data like CSV, easy to view on different mediums, free and open source, single file databases. It has to be this, right?
SQLite is wonderful, but it's definitely not a replacement for CSV
The main feature of CSV is that it's aways broken, not that it's almost trivial.
> with one that requires a specific 85 kLOC codebase to access
sqlite is available essentially everywhere. Every browser uses sqlite extensively internally, so do tons of other software on your standard desktop machine (to say nothing of mobile OS where it's ubiquitous). Using sqlite is not any sort of constraint.
> SQLite is wonderful, but it's definitely not a replacement for CSV
Only in the sense that it's nowhere near as bad and annoying as CSV.
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
CREATE TABLE temperature
(
ts integer,
Tc real,
Tf real,
src_id integer
);
INSERT INTO temperature VALUES(1615165342,5.5999999999999996447,42.099999999999999644,1);
INSERT INTO temperature VALUES(1615165350,0.6,32.999999999999998223,3);
INSERT INTO temperature VALUES(1615165404,5.5,41.899999999999995026,1);
INSERT INTO temperature VALUES(1615165410,-17.199999999999999289,1.0,2);
INSERT INTO temperature VALUES(1615165435,5.5,41.899999999999995026,1);
Or if you have SQLite installed, it is an easy to have SQLite itself read the dump and export it in CSV, letting it deal with things like quoting that can be a pain with grep and sed/cut. This way also makes it easy to rearrange or omit columns and to do some filtering so that data you don't care about doesn't get into the CSV.