So that is the asset pipeline in a nutshell. Separation of concerns, dependency management and optimization are added to turn the assets into first class citizens.
Capybara is a good way to do integration testing. The big advantage of Capybara is that it is possible to use different “driver” to run the tests. This makes it easier to test different browsers. Drawback is that it is kinda slow compared to Ruby testing. It does however have the same sexy syntax that you would expect from a testing framework.
Java or Coffee?
The beauty it though that it will work without CoffeeScript… if you want to! So, yes I’ll give it another go and maybe I’ll like it. If I do… expect another blog post on it ;-).