Use a build tool to get shit done.

So this moves the whole dev workflow to [Brunch](http://brunch.io).

Brunch is a popular build tool, main advantages of which are simplicity and speed. Some of Brunch advantages for this particular project:

1. You've stated you will want to move stuff to Coffee after some time — in Brunch, compilation is super-transparent, you don't need to think about anything. Not just coffee, same goes for less / stylus / sass / jade / handlebars / whatever.
2. No more “cache busting”. No more `a.js?4` etc. Built-in [optional] brunch webserver handles caching correctly. Same goes to GH-pages.
3. Dependencies are now mostly managed by [Bower](http://bower.io) package manager. Less stuff in repo = less time needed for new contributors to clone it to their drives (some projects make it horrible to contribute). Bower makes it super-simple to update deps.
4. Everything is concatenated automatically which means time needed to download all scripts is much less on slow connections.

New users will need to do three steps:

1. `npm install -g bower brunch`
2. `bower install && npm install`
3. `brunch watch --server`

[Deploy] `brunch build --production` if you want to build it for production (gh-pages) - everything would be minified etc.

New structure description:

1. Place scripts and styles in `app`, they will be concatenated to one style / script file.
2. Place things you want to be simply copied to output directory to `app/assets`
3. Output directory is `public`, it is also served by brunch webserver. You can safely remove it and it will be re-created on every build.
4. `bower_components` is auto-generated from Bower, `vendor` is for these dependencies which are not in bower yet.

README will need to be updated too, I will do this in the next PR.