anchor.diff:  
   In the future, the mapping will be more complex:
   
  -* The URL will start to include a checksum of the resource's content, e.g., +/assets/32fec9/css/style.less+.
  +* The URL will include a checksum of the resource's content, e.g., +/assets/32fec9/css/style.less+.
   * The URL may reflect the use of GZip compression, e.g., +/assets.gz/33839a/css/style.less+.
   
  -Because of this, when referencing assets inside your templates, you must pass paths through Twixt to get URIs that will work in the browser:
  +Because of this, when referencing assets inside your templates, you must pass paths (relative to +META-INF/assets+) 
  +through Twixt to get URIs that will work in the browser:
   
   [source,clojure]
   ----
  
positive.code: 
  In other words, when there's a failure, Twixt can tell you the steps that led up the failure, which is 90% of solving the problem in the first place.
  
  === How does Twixt differ from Dieter?
  
  On the application I was building, I had a requirement to deploy as a JAR; Dieter expects all the assets to be on the filesystem; I spent some time attempting to hack the Dieter code to allow resources on the classpath as well.
  
negative.code: == Twixt
  
  Twixt is an extensible asset pipeline for use in Clojure web applications.
  
  Twixt includes a very readable HTML exception report page, which displays:
  
  * The entire stack of nested exceptions, top to bottom
  * The stack trace for only the root exception
  * Demangled namespace and function names for Clojure stack frames (io.aviso.twixt/new-twixt/reify/middleware/fn instead of
    `io.aviso.twixt$new_twixt$reify__954$middleware__959$fn__960.invoke()`).
  * The contents of the Ring request map
  * All JVM system properties
  
  Twixt draws inspiration from http://tapestry.apache.org[Apache Tapestry] and https://github.com/edgecase/dieter[Dieter].
  
  