4 ms·
Long long ago, gzip would cause some browsers to barf. Some browsers would lie about what they could handle, and you had to check the UA as well as the accept-e
by litewulf 17y ago
Long long ago, gzip would cause some browsers to barf. Some browsers would lie about what they could handle, and you had to check the UA as well as the accept-encoding header.
JS/CSS concatenation, at least from the last time I had to roll my own always drove me nuts because I wanted to "recompile" on the fly and thus putting it in my build script meant I had to rebuild with every little change.
(I recognize these are excuses. But every action comes with an opportunity cost, blah blah blah)
- nostrademons 17y agoI often copy the uncompressed source directly over the compiled file, make my edits on the live file, and then copy it back when I'm ready to check-in. Granted, the system I work with compiles and doesn't concatenate, which is a slightly simpler problem. But you could easily have your build script leave comment markers in the file (or just look for top-level '(function(){...})()' closures which nearly every sane system uses) and "unbuild" the concatenated file from that.
- acdha 17y agoI think you might be overstating this a bit: browsers definitely had gzip support back in the stone-age (I actually implemented this by hand in 2000 or so) but for slightly shorter values of "long, long ago" it's also been the case that the necessary UA checks were well-known even if your default Apache config didn't already include them. JS/CSS, however, I agree completely on - it's a good deployment step but minification is quite the nuisance for debugging and it's less critical if you've configured your server to set proper Expires/Cache-Control headers.