Boud<p><span class="h-card" translate="no"><a href="https://mastodon.social/@leibnizopenscience" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>leibnizopenscience</span></a></span> </p><p>The paper seems to have missed a powerful workflow language: <a href="https://framapiaf.org/tags/Make" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Make</span></a> [1], with <a href="https://framapiaf.org/tags/GNUMake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GNUMake</span></a> [2] being the canonical example. It's stable and nearly half a century old. Learn and use it now and your scientific grandchildren will be able to reproduce your workflow in 2075 [3]. <a href="https://framapiaf.org/tags/Maneage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Maneage</span></a> [3][4] uses Make for *both* reproducible software + reproducible workflows.</p><p>[1] <a href="https://en.wikipedia.org/wiki/Make_%28software%29" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Make_%28</span><span class="invisible">software%29</span></a></p><p>[2] <a href="https://gnu.org/software/make" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">gnu.org/software/make</span><span class="invisible"></span></a></p><p>[3] <a href="https://maneage.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">maneage.org</span><span class="invisible"></span></a></p><p>[4] <a href="https://doi.org/10.1109/MCSE.2021.3072860" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">doi.org/10.1109/MCSE.2021.3072</span><span class="invisible">860</span></a></p>