I'm really glad to see Heroku focusing on these types of optimizations. We've been using similar optimization strategies internally at my Rails consultancy for

I'm really glad to see Heroku focusing on these types of optimizations. We've been using similar optimization strategies internally at my Rails consultancy for over a year [1], and it's amazing how much fun it is to ship features when you can add a small feature, check your test suite via CircleCI, and be live quickly thereafter. I remember the pain of deploying Huckberry [2] on Rails 3 a couple of years ago. Each deploy took ~6 minutes, and it'd drive us crazy. A whole lot of "Compiling!"-type [3] moments. (Back then, the Asset Pipeline compiled all of your assets twice: once with the real filename, once with the digest-filename: 'filename--f74c093df554be59d45d3c87920eba1f.js'. As you can imagine, this was quite slow.) This is one of the reasons I really love Heroku as a development platform. We're a 4-person shop—we can't spin off a resource to spend 2 weeks speeding up our deployment process. But with Heroku, we wake up one morning, and our processes our 40% faster. It's fantastic. [1] https://github.com/heroku/heroku-buildpack-ruby/pull/96 https://github.com/heroku/heroku-buildpack-ruby/pull/96 [2] https://secure.huckberry.com/ https://secure.huckberry.com/ [3] https://xkcd.com/303/ https://xkcd.com/303/ [edit: formatting]