Show HN: Cr – Runs your tasks at maximum concurrency

Re:Show HN: Cr – Runs your tasks at maximum concurrency by haldean on Monday December 18, 2017 @02:38PM (#15954710)

And tup for the last 10. Lots of people in this thread complaining about Make's syntax might want to check it out; it has a nice, simple "inputs |> command |> outputs" syntax, a similar "output the DAG" mode to Cr, and defaults to parallelism.

http://gittup.org/tup/

[ Parent | on HN ]

Re:Show HN: Cr – Runs your tasks at maximum concurrency by aidenn0 on Monday December 18, 2017 @03:47PM (#15955349)

That's funny because I would list tup's syntax as a negative for an otherwise very useful tool.

Also, Tup is much more single-purpose than Make or (from a quick readthrough) Cr. It is very strongly focused on the "N files in, 1 file out" for compilation, and specializes at that to the point of not doing other things.

As far as a minimal "better make" I find redo to be the best. Make is a weird combination of the shell and makefile languages, but redo boils it down to just a single language and manages to handle dependency of build rules in an elegant manner.

[ Parent | on HN ]

Re:Show HN: Cr – Runs your tasks at maximum concurrency by dilap on Wednesday December 27, 2017 @08:22PM (#16019575)

curious, which variant of redo do you actually use?

[ Parent | on HN ]

Re:Show HN: Cr – Runs your tasks at maximum concurrency by CJefferson on Monday December 18, 2017 @04:30PM (#15955693)

I love tup, but I find too many places where it doesn't work to use it for things I distribute (sometimes fuse fails, doesn't work on Linux subsystem for Windows, flakey on full windows).

[ Parent | on HN ]