Modd: a flexible tool for responding to filesystem change (opens in new tab)

I chose to build the commands into the file with a comment rather than add an extra config file. For your test-compile cycle for Go, I think that would look like this at the top of each of your go files:

# autorun go install ./cmd/devd

modd looks like it has the advantage of only specifying this one, and specifying commands to be run when modd first starts up (autorun only has one type of command that's run on startup and on file changes).

Here's a Java article describing its internals: http://www.javaadvent.com/2015/12/reactive-file-system-monit...

The only caveat I got, and this is completely due to my inexperience with Go, is to not use `daemon: go run foo.go`, but to `prep: go build foo.go; daemon +sigint: ./foo`

Another good use is to restart webpack when a non-hot-replaceable file changes:

  /projects/foo/src/index.js {
      daemon +sigint: npm start
  }

http://mitmproxy.org

Tup on Windows doesn't support monitoring for source changes. This will fix that nicely I guess.