Sprockets 2.0.0 released (Ruby/Rack asset packaging)

Sprockets provides the basis for Rails 3.1's asset pipeline.<p>For a look back in time, see the Hacker News thread for Sprockets 1.0, from two and a half years ago: <a href="http://news.ycombinator.com/item?id=487601" rel="nofollow">http://news.ycombinator.com/item?id=487601</a><p>Some alternatives include the very popular Jammit from DocumentCloud (<a href="http://documentcloud.github.com/jammit/" rel="nofollow">http://documentcloud.github.com/jammit/</a>), Alex MacCaw's Ruby port of Stitch (<a href="https://github.com/maccman/stitch-rb" rel="nofollow">https://github.com/maccman/stitch-rb</a>), and Mislav Marohnić's "poor man's Sprockets" (<a href="https://twitter.com/#!/mislav/status/87899513649496065" rel="nofollow">https://twitter.com/#!/mislav/status/87899513649496065</a>).

Is there somewhere that gives a good description of the current state of asset packaging in Rails? Personally, I find the whole thing really confusing.<p>Right now, I'm just using asset_id (<a href="https://github.com/moocode/asset_id" rel="nofollow">https://github.com/moocode/asset_id</a>) to dump my assets on S3/CloudFront with md5s in the filenames, pretending to myself that that will make everything fast.<p>It seems like all the gems provide different things, whether it's CSS minification, JS minification, includes to combine many files together, automatic aggregation of multiple JS/CSS files, CSS sprites, easy uploading to CDNs, different strategies for cache busting (md5 of file vs node timestamp)...<p>I'm presuming that with Rails 3.1, everyone is going to switch over to Sprockets 2.0 from Jammit (which is what it seemed like everyone used before). However, I honestly have no idea what's going on or where the big wins are.<p>What's up?