Re:Bash 5.0 released
by chrisshroba on Monday January 07, 2019 @11:20PM
(#18853117)
It seems like this would eliminate the need to read a file from disk and fork a new process, both of which take time. If you're just removing a single file, this is probably negligible, but if you have a script iterating over 10k files, i.e., this speed-up may be more welcome.
[ Parent
| on HN ]
> if you have a script iterating over 10k files
That's probably a good sign you should advance from shell. If the script is trivial, it's going to be trivial in python / ruby / go / crystal / ... as well. If it's not trivial, that's another reason to move.
I agree that as scripts get more complex, you should migrate from bash. But the number of files a script touches says almost nothing about its complexity.
Wasn't saying otherwise. One reason is complexity. Another is performance.
True, but if you are iterating over 10k files and removing them, then a find|xargs pipe with xargs feeding rm the maximum number of parameters the kernel allows per fork will likely be faster than a bash interpreter loop, even with a bash builtin rm.
You think find|xargs would be faster than (gnu) find -delete?