Friendly suggestions

Ok, so I saw @datachomp open this project up.  I took a look, and I thought I'd throw in a few suggestions.  

I did this while watching tv, so don't trust everything... my attention was spread out.  

There are a billion examples of this, but I've used this ```respond_to``` format stuff example **0** times in production.

The non-Rails Reason is that our sites are usually responsive, so mobile/tablet users the same view.

The first Rails Reason is that, to me, that block is very difficult to test.  If you were to unit test it, you'd have to throw a mock into the block passed to the faked method on the controller, then verify ... yawn.  If it's hard to test, why write it???

The second Rails Reason is that if you don't write this block, then... you don't have to replace it with anything.  Rails will, by default, run the ```render params[:action]```.

The third Rails Reason is... it's a nice idea to slop in the ".xml" on the end of a URL and get the XML representative of an object, but it's not very practical.  The details and needs of APIs are different than HTML pages, and as a consumer of many APIs... I'd rather do something API-specific with versioning and different authentication and the like.  (I say this because the "responds to XML, responds to JSON" examples are the other common use for ```respond_to```