Using the query string to bust cache and replacing your assets on deploy is the simple solution that Rails' asset pipeline replaces.

Rails' asset pipeline doesn't delete old assets. That way you don't get inconsistencies when not all of your servers symlink to the new assets at the same moment.

That's pretty cool. :)

> No sense of humor? Oh right, HN.

I'll start laughing when you start being funny.

> Nope. Catenating files has been the privilege of Unix users since the 70s, that we would believe this to be difficult or complicated is embarrassing. The trickier part was sedding the query string that invalidates the old versions.

Ooooh! Colour me embarrassed, you got me there champ!

Lose the hostility man, it's not needed.

What about rolling up assets seems so irreducibly complex that you want to rely on a shake-n-bake to get 'er done?

You just need to learn the key to winning debates against other software devs: The first to snark wins!