anchor.diff:  
   === Why another routing library?
   
  -Just because the existing ones are to complex and with very bloated documentation
  -that does not explains the essential for the basic use of library.
  +Existing solutions out there are complex and generally bloated wih irrelevant
  +documentation.
   
  -Many other libraries are focusing on using clojure data structures for represent the
  -routing in some kind of tree. The concept is very nice but in practice, when you
  -have complex routing paths, the things becomes dificult to read and understand at
  -quick view.
  +Most libraries work with native Clojure data structures for representing the
  +routing configuration. It's a great idea, but it does not work very well once
  +your proyect scales. Things get out of hand pretty fast.
   
  -Let see a real example using *bidi* routing library:
  +An example of this with link:https://github.com/juxt/bidi[bidi] routing library:
   
   [source, clojure]
   ----
  
positive.code:    ["/workspace/:project-uuid/:page-uuid" :workspace/page]])
  ----
  
  Of course, just now *bide* does not offers all the features that the other
  libraries, and many of missing stuff will be added over time. But the main purpose
  of bide is to stay *small and simple*.
  
  
  == How fast is *bide*?
  
negative.code: ----
  
  
  Now, you can perform basic operations such as `match` and `resolve`:
  
  [source, clojure]
  ----
  