drop coffeescript

[git-j]

The use of coffeescript is unintuitive and makes no sense with a js-centered development stack (eg node.js - express - backbone - jquery) introducing the coffeescript dependency makes the code hard to maintain without a correct build environment. The only advantage of coffee as the source-language is that it enforces a javascript-style that can be considered consistent.

this would require the following steps:

• cake build the latest source
• copy all documentation from coffee into the output javascript
• split up the output javascript into multiple files
• implement unit tests
• implement code style enforcement
• use requirejs or amd for loading the multiple files
• use uglify/minify/concat grunt rules to build a 'production.js'

optimistic ETA: 32hrs, pessimistic ETA*3