This post is here to prevent broken links, since I’ve noticed people coming here from a link to my old Stakeout page.
Stakeout was a program that runs something when files change, by watching for file changes at the system level using kqueue. It was intended to support running automated tests. The 2nd version even worked with growl to pop up info about the test success or failure.
I still have the Stakeout-2 tarball available, but I haven’t tested it in years.
Why? I’ve been working on things that take too long to test, so I don’t want to run a suite every time a file changes anymore. I still think it’s a useful idea.
Nicholas Riley 7:51 pm on September 7, 2009 Permalink |
This is kind of the point of services like Google App Engine. Unfortunately they still make you worry about scale before you really need to.
And yeah, it’s really hard to resist the tinkering urge. I spent an hour last week trying to hack up an application interface to Quick Look to let me go full-screen. (The documented APIs aren’t very flexible and the undocumented ones are overcomplicated. It didn’t go very far.)