Rails provides great performance and when coupled with Apache/Nginx delivering Assets is not that big of a deal. But as Heroku doesn't provide any proxying it

Rails provides great performance and when coupled with Apache/Nginx delivering Assets is not that big of a deal. But as Heroku doesn't provide any proxying it is upon every developer to implement something like this. Though doing it takes probably less than an hour, so compared to earlier times it is incredibly easy. And someone else already mentioned that this is not something you would do from day one. The first deployment (especially with Heroku) is incredibly easy, but there is a lot to build upon once you have that application up and running.