I have spent a lot of hours looking at `watch "xsv select ... | xsv table"`.
They are very good tools but I now prefer duckdb for CSV processing.
Not that there is necessarily that much churn in csv processing, but last I looked, the xsv repo has not received much maintenance for a while.
This is an active fork: https://github.com/dathere/qsv
Never realized it was a fork. qsv is great. I parsed lots of 4Gb files with it and was really happy.
There's also DSQ which uses SQL instead of its own language.
https://github.com/multiprocessio/dsq
When software is feature complete, fast and working correctly, what is it exactly you expect to change?
I mean there are 131 open issues and some 30+ PRs, so clearly people have some desire for change.
No criticism to the author. He is way more productive than I will ever be, but xsv does appear to be on the back burner. Open source means the author can spend their time how they like and I am entitled to nothing.
https://www.hackerneue.com/item?id=43494894 discusses xan
https://github.com/medialab/xan
readme says this tool is originally a fork of BurntSushi's xsv, but has been nearly entirely rewritten at that point, to fit SciencesPo's médialab use-cases, rooted in web data collection and analysis geared towards social sciences (you might think CSV is outdated by now, but read our love letter to the format before judging too quickly). xan therefore goes beyond typical data manipulation and expose utilities related to lexicometry, graph theory and even scraping.
IIRC it was just deprecated in nixpkgs for this reason
[1] rows included linebreaks so your standard sed/head/tail/something-from-coreutils approach would not work.