Good point. Delegating to the storage backend instead of using a STATIC_URL is a don't-repeat-yourself solution.

It's interesting that the CachedStaticFilesStorage will replace urls inside of CSS (as part of the time-stamping), but the standard Storage won't do it to change paths for development/production. As it stands, I use production urls in CSS so that I don't have to change it when I deploy.