Jammit should already be playing well with Rails' built-in cache busting, although I imagine that the situation might change with 3.1's new fingerprinting. As

Jammit should already be playing well with Rails' built-in cache busting, although I imagine that the situation might change with 3.1's new fingerprinting. As for having to pipe "static" JS and CSS files through ERB ... I've always thought that was something best avoided by choice, unless absolutely necessary.