Their first suggestion, and the one they are definitely implicitly recommending, is: "Use it as a part of your asset packager to compile templates ahead of time..."
$ curl http://goo.gl/OCK7V
<HTML>
<HEAD>
<TITLE>Moved Permanently</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Moved Permanently</H1>
The document has moved <A HREF="http://twitter.github.com/hogan.js/1.0.0/hogan.js">here </A>.
</BODY>
</HTML>
$ curl -I http://goo.gl/OCK7V
HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Expires: Thu, 22 Dec 2011 18:18:46 GMT
Date: Thu, 22 Dec 2011 18:18:46 GMT
Cache-Control: private, max-age=86400
Location: http://twitter.github.com/hogan.js/1.0.0/hogan.js
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Server: GSE
Transfer-Encoding: chunkedJust because nobody explicitly said it - a 301 redirect is actually cacheable per §10.3.2 of RFC 2616. But google doesn't set a long cache duration - another one of your responders posted the response headers, it was 86400s which is 1 day.