4 ms·

For a better "make" try "do" (also known as "DJB redo"). It's designed by Dan Bernstein of crypto fame and implemented by Avery Pennarun now at Google. http:/

by jph 9y ago

For a better "make" try "do" (also known as "DJB redo"). It's designed by Dan Bernstein of crypto fame and implemented by Avery Pennarun now at Google. http://apenwarr.ca/log/?m=201012#14 http://apenwarr.ca/log/?m=201012#14 I will contribute $100 to any Rust leader who wants to start coding "do" in Rust.

mitch9 9y ago
This seems like a prime moment to ask for a review of https://github.com/sagebind/rote https://github.com/sagebind/rote
- jph 9y ago
  Rote is a great accomplishment. IMHO it's superior to Make, Rake, Cake, etc. Thank you for writing this! If you're curious, take a look at Do. It's like all of the above, yet flipped over on their heads. The value of Do is in the design, which is essentially the opposite of Make. Do leverages the composability of items, files, scripts, artifacts, and typical Unix pipes. I would be very interested in your opinions about Do, and if you want the $100 to jumpstart working on Do in Rust, let me know how to donate to you.
zimpenfish 9y ago
+1 for do/redo. Although it can be a bugger to get right for go (because there's no intermediate files) (although I think I've solved that now.)
- sounds 9y ago
  I looked at your profile, but didn't see any clues. Please share? How do you use redo for go projects?
  - zimpenfish 9y ago
    [looks at pending blog posts guiltily] https://bitbucket.org/rjp/can-x-win/src https://bitbucket.org/rjp/can-x-win/src is a good example - basically, apart from `all.do` containing the targets, I have a `default.do` which looks for a matching `*.od` which has the DEPS and then passes those to `go build`.
JdeBP 9y ago
That's somewhat misleading. * http://jdebp.eu./FGA/introduction-to-redo.html http://jdebp.eu./FGA/introduction-to-redo.html * https://news.ycombinator.com/item?id=15060193 https://news.ycombinator.com/item?id=15060193

4 ms·

For a better "make" try "do" (also known as "DJB redo"). It's designed by Dan Bernstein of crypto fame and implemented by Avery Pennarun now at Google. http:/

by jph 9y ago

mitch9 9y ago
This seems like a prime moment to ask for a review of https://github.com/sagebind/rote https://github.com/sagebind/rote
- jph 9y ago
  Rote is a great accomplishment. IMHO it's superior to Make, Rake, Cake, etc. Thank you for writing this! If you're curious, take a look at Do. It's like all of the above, yet flipped over on their heads. The value of Do is in the design, which is essentially the opposite of Make. Do leverages the composability of items, files, scripts, artifacts, and typical Unix pipes. I would be very interested in your opinions about Do, and if you want the $100 to jumpstart working on Do in Rust, let me know how to donate to you.
zimpenfish 9y ago
+1 for do/redo. Although it can be a bugger to get right for go (because there's no intermediate files) (although I think I've solved that now.)
- sounds 9y ago
  I looked at your profile, but didn't see any clues. Please share? How do you use redo for go projects?
  - zimpenfish 9y ago
    [looks at pending blog posts guiltily] https://bitbucket.org/rjp/can-x-win/src https://bitbucket.org/rjp/can-x-win/src is a good example - basically, apart from `all.do` containing the targets, I have a `default.do` which looks for a matching `*.od` which has the DEPS and then passes those to `go build`.
JdeBP 9y ago
That's somewhat misleading. * http://jdebp.eu./FGA/introduction-to-redo.html http://jdebp.eu./FGA/introduction-to-redo.html * https://news.ycombinator.com/item?id=15060193 https://news.ycombinator.com/item?id=15060193