xsv VS ripgrep

qsv is a command-line tool to work with CSV files. It is the successor of xsv and is written in Rust. Current progress is quite impressive as qsv now has SQL and Lua support.

Let's say, we want to write an extension that lists all the repositories of the user. The extension is a simple shell script that uses the gh command to list the repositories current user owns and tabulates with xsv command:

I cannot imagine any way it is worth anyone's time to follow this article's suggestion vs just using something like zsv (https://github.com/liquidaty/zsv, which I'm an author of) or xsv (https://github.com/BurntSushi/xsv/edit/master/README.md) and then spending that time saved on "real" work

I realize it's not really that comparable since these tools don't support SQL, but a more fully functioned CLI tool is - https://github.com/BurntSushi/xsv

They are both fairly good

I have done some similar, simpler data wrangling with xsv (https://github.com/BurntSushi/xsv) and jq. It could process my 800M rows in a couple of minutes (plus the time to read it out from the database =)

xsv, which seems to be why qsv was created.

[1] https://github.com/BurntSushi/xsv/issues/267

CSV utilities (still haven't pick a favorite one...): https://github.com/harelba/q https://github.com/BurntSushi/xsv https://github.com/wireservice/csvkit https://github.com/johnkerl/miller

I'm the author of Biff. I just wanted to leave a really cool example of something that Biff can do that I _think_ is kinda hard to do otherwise. (And also, I want to make an assertion about it and I hope this will lead to me being wrong and learning something new.)

The use case is: "I want to see a list of all files in a repository, sorted in ascending order of when it was most recently changed according to source control. I also want to highlight the time with color, make it be in local time and format it in my own bespoke way using strftime." Here's the full command (run from the root of https://github.com/BurntSushi/ripgrep):

    $ git ls-files \

For full-text search, ripgrep is faster than any in-app search I've used:

ripgrep – A fancier version of grep commonly used by coding tools.

After finding files, I usually need to search inside them. For that, ripgrep, usually called rg, is my default.

Ah yes... its `-E`.

But fastmod, which is mentioned in at the end of https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#search-and-replace is surprisingly good, both in terms of performance/ux and compatibility.

You just:

  fastmod -m 'something I need to (change|break)' '$1 is inevitable'

BurntSushi/ripgrep

ripgrep needs no introduction. It's grep, but fast. Respects .gitignore, searches recursively by default, and returns results before you finish blinking.

Ripgrep does something like thhis. It has a meta regex engine that switches engine when it finds what looks like pathological cases (or rather, the regex-automata crate does, which is used by the regex crate, which powers ripgrep).

https://docs.rs/regex-automata/latest/regex_automata/meta/st...

Ripgrep in turn exposes some knobs to tweak the heuristics

https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#how...