GNU Parallel

Post by musicale » Sun, Apr 03, 2022, 12:10 AM UTC

dehrmann wrote: post #2

It's nice, but the citation bit strikes me as very non-free: > If you use --will-cite in scripts to be run by others you are making it harder for others to see the citation notice. The development of GNU parallel is indirectly financed through citations, so if your users do not know they should cite then you are making it harder to finance development. However, if you pay 10000 EUR, you have done your part to finance…

    for util in /usr/annoying/bin/*; do
        touch ~/.$(basename $util)/stfu
    done

Post by musicale » Sun, Apr 03, 2022, 12:29 AM UTC

krapht wrote: post #30

musicale wrote: post #28

Earlier quoted context omitted.

I don't care what GNU thinks, but it's simply not scalable. Imagine a world where every utility has its own irritating nag message that needs to be turned off.

Don't need to imagine, I lived in that world where most utilities I used were shareware with a nag screen on startup...

Post by arrakeen » Sun, Apr 03, 2022, 1:15 AM UTC

cb321 wrote: post #22

ZoomZoomZoom wrote: post #17

Earlier quoted context omitted.

> Anyway, those three are just off the top of my head, unfairness-wise. Last I looked at the source for GNU parallel it looked like mountains upon mountains of Perl I would rather not depend upon, personally, but to each his own. Well, there was a Rust version with zero Perl, now unfortunately archived. It wasn't 100% on a par with the original and wasn't really finished. On the other hand, built easily for Windows a…

Well, some archived project is not so great either. The core functionality is not even a 20 line bash script since bash grew wait -n, though: #!/bin/bash if [ "${1-0}" -lt 1 ]; then # No arg / arg not a number >= 1 echo "Usage: $0 "; echo "reads cmds from stdin, running up to N at once." exit 1 fi TMP=`mktemp -t stripen.XXXXXX` trap 'rm -f $TMP; exit 0' HUP INT TERM EXIT STRIPE_SEQ=1 while read cmd; do jobs > $TMP #…

Post by smegsicle » Sun, Apr 03, 2022, 1:38 AM UTC

cb321 wrote: post #12

WhatIsDukkha wrote: post #6

This can be a good entry into the "why" for many people that use xargs now - https://www.gnu.org/software/parallel/parallel_alternatives.... It has a lot of features that can feel excessive at first glance but if you have felt some pain in building jobs, most of it is pretty sensible and much better than rollyourown.

The comparison is not very fair to modern day xargs. `nproc` is a relatively standard utility (coreutils). So, xargs -P$(nproc) gets you core (or core-proportional) parallelism. Grouping output/Making a safe parallel grep is also easy-ish with `--process-slot-var=slot` and sending to `tmpOut.$slot`. Jobs on remote computers can be done similarly with any kind of `arrayVar[$slot]` setup where `arrayVar` has a bunch of…

Post by dehrmann » Sun, Apr 03, 2022, 3:24 AM UTC

musicale wrote: post #33

krapht wrote: post #30

Earlier quoted context omitted.

Don't need to imagine, I lived in that world where most utilities I used were shareware with a nag screen on startup...

I think I'll pass on GNU/Linux: Shareware Edition.