anchor.diff:  <1> Render the html table
   <2> Render the javascript
   
  -Maybe we need to drop the client side of the plugin if it is too much work, but i always liked the easy setup with the
  +Maybe we need to drop the client side of the plugin if it is too much work, but I always liked the easy setup with the
   tables.
   
   === Server side
  
positive.code: 
  == Usage
  
  Here i want to discuss the proposed usage of the API. In general i would prefer to concentrate on a single route
  functionality so we can transfer all server side settings into the view without declaring it twice.
  
  Nevertheless I would also offer the possibility for two routes, which will require more configuration from the developer
  
  === Single Usage
  
  
negative.code: 
  === Internal usage
  
  Internally I would like to change the structure to be more flexible.
  E.g. we should only have one method that will accept the data `Datatable::data($provider)`
  where the `$provider` will provide all the extra operations on the object.
  
  I would also like to make the api more fluent.
  