4 ms·
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than i
by jashkenas 15y ago
The 3.1 asset pipeline is great stuff ... but if anyone currently using Jammit is leaning towards switching to the asset pipeline -- for any reason other than it's the default in Rails 3.1 -- I'd be curious to hear about why. I'd like to keep developing Jammit as an alternative approach, as there are differences in philosophy: explicit asset packages vs. in-file dependencies, for example.
- nixme 15y agoJammit has worked extremely well paired with Barista+Compass, but for a Backbone-heavy app where templates are shipped client-side, it's nice to tack on '.erb' at the end of a template file and use Rails asset helpers for cache-busting and asset host url construction.
- jashkenas 15y agoJammit 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.