Big files #21
Description
Imagine you have a huge file that you want to transform/filter. It won't fit in memory.
One might expect that using the -S option solves their issue. They try, and discover it does not. Instead they'll have to split the huge file using other tools, only then are they able to use Ramda-cli.
Does Ramda-cli want to cover the use case of files which exceed the size of memory?
jq is a tool which can solve your issues. Assuming Ramda-cli will support bigger files, it can compete/compliment jq:
- People can leverage their existing JS and Ramda experience to make parallelized shell pipelines.
jqdoes not have a good use case for performing aggregations. FP and Ramda-cli makes this easy.