Everyone is going to compare it to Make, but it's not like Make syntax is ideal or consistent; I can see this being especially useful when using it in part of a pipeline, where maybe the YAML is generated elsewhere.
I miss read this, I thought it was an implementation of workers with a dependency graph.<p>for similar projects look at:<p>Bazel <a href="https://bazel.build/" rel="nofollow">https://bazel.build/</a><p>Tup <a href="http://gittup.org/tup/" rel="nofollow">http://gittup.org/tup/</a><p>Make <a href="https://www.gnu.org/software/make/" rel="nofollow">https://www.gnu.org/software/make/</a>
This is awesome. I have been working on something similar, but added a UI to visualize the tasks and the order they ran in.<p><a href="https://www.gabrielcsapo.com/build.sh/" rel="nofollow">https://www.gabrielcsapo.com/build.sh/</a>
Looks nice! Will inspire my project as well. Made something recently as well which is based on the same principle. A simple parallel/sequential task runner which has built in retries and allows steps to be continued even if they return errors.<p><a href="https://github.com/abelmokadem/scriptz" rel="nofollow">https://github.com/abelmokadem/scriptz</a>
I'm sure somebody has a use for this. But with no scheduler tuning, no prioritization, no dynamic configuration, no multiprocess logic, etc it's effectively just "xargs" with dependency tracking, written in Go. And I'm pretty sure you can do this with Ansible.
A co-worker of mine recently implemented something very similar.<p>Our major feature over Make was emitting events as newline separated JSON, so that a downstream process can visualize them in a pretty way, track progress, etc.<p>We use ours run multiple Chef recipes in parallel.
I thought it was related to this:<p><a href="https://github.com/fungos/cr" rel="nofollow">https://github.com/fungos/cr</a><p>It was recently over Twitter.