json-toolkit VS nq

CSV is great because excel can import it, but it can't import USV, so at that point, why use USV when you can use JSON?

https://github.com/tyleradams/json-toolkit/

> Also note that this approach generalizes to other text-based formats. If you have 10 gigabyte of CSV, you can use Miller for processing. For binary formats, you could use fq if you can find a workable record separator.

You can also generalize it without learning a new minilanguage by using https://github.com/tyleradams/json-toolkit which converts csv/binary/whatever to/from json

I really like this tool, but I'm not sure what it gets me more than jq (and https://github.com/tyleradams/json-toolkit to convert non-json to json).

What can angle grinder do better than jq?

If you want something quick and janky, I suggest nq. It's stupidly simple and lightweight; it just requires that everyone is running as the same user. And only lets exactly one job of any kind run in a given queue. There's basically zero configuration; just nq , and it'll either start running , or will wait its turn.

For your ad-hoc uses, I would introduce nq. It's an extremely lightweight queuing system, which gives you two things with minimal overhead:

I'm already aware of alternatives which I will consider (at, nq, snooze, but I still want an accurate lightweight CLI stopwatch/timer app and the script otherwise works well--this is more of an exercise on understanding background processes and could be handy in other scripts. Or if the attempt is considdered hacky and ill-advised, I'm curious of an alternative implementation. I just feel nothing is more simple than a very lightweight C-based timer app that exits 0 after specified time has elapsed and don't want to run a cron job or even a while sleep 1 loop for a reminder (sleep isn't even a builtin...).

Interesting project. Unfortunate that its name conflicts with one of nq’s executables (https://github.com/leahneukirchen/nq), but I’m not sure anything can be done about it.

nq