Avdi Grimm

I'm not convinced how much need there is for inheritance. It seems to me any shared-functionality scenario is handled at least, if not more, cleanly by factoring out a module....

Either that or just have the parent be a positional argument, similar to how `Class.new(Parent)` works. ``` ruby action :create(:new) do # ... end ```

Ubuntu 11.10 here. Chrome crashes, Firefox just loads endlessly when pointed at a hoof hostname.

You don't want that. I'm the worst maintainer ever, that's why I give away all my OSS projects to people who actually keep up with their email.

For performing one-off operations in the exact same context that Rake tasks run in (loaded libraries, whatever constant initialization is triggered by the Rakefile loading, etc.) Sometimes you want to...

(For comparison, GNU Make's `--dry-run`/`-n` prints the commands it WOULD execute, without executing them.)

Cool!!!

(I'm mostly just capturing some TODOs for myself here as I find features I'd like to contribute)

> Does this does not work? > > ```ruby > task "foo" do > sh({ "FOO" => "BAR" }, "ls manuscript/*.md > mdlist.txt") > end > ``` There are reasons...

Hi @brendangregg! Since diving into the world of BPF I've been having some "oh it was THAT Brenden Gregg that I hung out with in Australia" moments 😅