I actually agree with most of this. I tend to use Marcel for ETL sorts of processing, quick database access with data munging on either side, cluster access, etc. it works fine for basic shell usage though.
As for a more complex example: yes, the website has better examples, but they are also more involved to explain.
Almost forgot: I also switch from bash to Python at a low threshold. In that case, I find Marcel’s API useful. I can then do shell-like piping inside of Python.
Using the output of find into another program is not safe due to risk of file names containing delimiters. You need to use find -exec.
Good example of why machine readable output is important. Agree that the tutorial should showcase more and larger such examples.
You can always use -print0. I suppose there is some risk of a null slipping into a filename but I’ve never come across it myself.
> some risk of a null slipping into a filename
Only in some fairly esoteric environments: https://en.wikipedia.org/wiki/Filename#Comparison_of_filenam...
Yes, I know that, but it's also exceedingly rare for a filename to contain a newline and using -exec is extremely inefficient. I also wrote that on my iPad. Typically I'd use a combination of -print0 and xargs -0 for anything more formal than a one-liner on the command line.
The larger bug in my example is that it fails if any of the directories in the path contain a "." in their name!
So then why are you using such buggy examples as counterarguments?
It's one example. I didn't realize the mistake when I wrote it. I wrote my comment in good faith. What's with the interrogation?
This is a neat project though. I'll keep an eye on it.