Show HN: Introducing Harp – A static web server with built in preprocessing
"Build on request" is a good idea. We do something similar in our stack: tup[0] as the (insanely fast) build system, and developer VMs run mitmproxy[1] on port 8080 which runs tup before every request.<p>I prefer this style of a setup to coupling them together a-la Harp. If the webserver doesn't work out, I can swap it out. Same with the build system. Tying them together makes me antsy. And for good reason I think: since 2004, we have switched from Apache -> Lighttpd -> Nginx, and have switched from custom shell scripts -> Make -> Tup (with some fabricate.py, and with calls out to other build systems like Leiningen)<p>[0] <a href="http://gittup.org/tup/" rel="nofollow">http://gittup.org/tup/</a><p>[1] <a href="http://mitmproxy.org/" rel="nofollow">http://mitmproxy.org/</a>