If you're using GNU Parallel for simple, non-parallel command line tasks and scripting, I've written a tool which I find to be much more intuitive: https://github.com/Miserlou/Loop The author of GNU Parallel wrote a pretty detailed comparison, which you can find in the linked README.
Your tool looks nice, but it doesn't seem to parallelize the work in any way.
GNU Parallel Cheat Sheet [pdf]
21–30 of 64 posts
Re: GNU Parallel Cheat Sheet [pdf]
#22Ah, the rare case of nagware in GNU. From the man page: "--citation Print the BibTeX entry for GNU parallel and silence citation notice. If it is impossible for you to run --bibtex you can use --will-cite. 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 no…
Your criticism would be fair if FOSS authors were rightly conpensated for their work. This isn't nearly the case, so until then blaming FOSS authors for some experimentations is just unwarranted.
Citing it or not is an issue of academic practice/considerations (whether its use was a significant part of the research etc.). Mandating it through nag messages is too much.
What's next? make will print ads while the compilation runs? GIMP will watermark my images if I don't pay 10K or promise to cite it if I make figures with for my paper?
So again, my main confusion is about how this can be an official GNU tool.
Re: GNU Parallel Cheat Sheet [pdf]
#23I've never used GNU Parallel. But could someone explain to me the value add vs GNU xargs -P/--max-procs? From the examples at the top, it seems like those could be achieved with xargs.
Re: GNU Parallel Cheat Sheet [pdf]
#24Still often the simplest way to get parallel computation in python, sadly.
Re: GNU Parallel Cheat Sheet [pdf]
#25Ah, the rare case of nagware in GNU. From the man page: "--citation Print the BibTeX entry for GNU parallel and silence citation notice. If it is impossible for you to run --bibtex you can use --will-cite. 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 no…
Re: GNU Parallel Cheat Sheet [pdf]
#26Earlier quoted context omitted.
Your criticism would be fair if FOSS authors were rightly conpensated for their work. This isn't nearly the case, so until then blaming FOSS authors for some experimentations is just unwarranted.
They can do experimentations and distribute their work through their channels then. But GNU tools (and FOSS by extension) are so popular because of their no-nonsense philosophy of here it is do with it whatever you want. Run it anywhere and any way you please. Citing it or not is an issue of academic practice/considerations (whether its use was a significant part of the research etc.). Mandating it through nag messag…
Re: GNU Parallel Cheat Sheet [pdf]
#27Re: GNU Parallel Cheat Sheet [pdf]
#28Ah, the rare case of nagware in GNU. From the man page: "--citation Print the BibTeX entry for GNU parallel and silence citation notice. If it is impossible for you to run --bibtex you can use --will-cite. 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 no…
Re: GNU Parallel Cheat Sheet [pdf]
#29Parallel is Good Stuff (tm) and works very well but I haven't had much cause to use it. For ad-hoc system modifications I've found myself using tmux's synchronize-panes feature, or xargs. For anything bigger or more involved then I break out Ansible/Chef/Puppet depending on which client project I'm working on. I remember one place I worked at had a huge elaborate configuration/deployment system hand written by the he…
Re: GNU Parallel Cheat Sheet [pdf]
#30Earlier quoted context omitted.
Your criticism would be fair if FOSS authors were rightly conpensated for their work. This isn't nearly the case, so until then blaming FOSS authors for some experimentations is just unwarranted.
They can do experimentations and distribute their work through their channels then. But GNU tools (and FOSS by extension) are so popular because of their no-nonsense philosophy of here it is do with it whatever you want. Run it anywhere and any way you please. Citing it or not is an issue of academic practice/considerations (whether its use was a significant part of the research etc.). Mandating it through nag messag…