I would have to agree with you. If you're *already* gzip-ing your JavaScript, then packing doesn't make much sense. That said, the packed version is great for those that either don't know how to set up their server to do that, or don't have that kind of control (i.e. shared hosting).
Also, certain versions of IE6 have major issues with gzip-ed content (can't remember whether it's all gzip-ed content or just JS). On 4/10/07, Steve Spencer <[EMAIL PROTECTED]> wrote:
I'm sure this has been covered before, but if your web server is set to compress javascript automatically, is it worth it to pack jquery.js with the extra time spent unpacking? Simple case in point: Start with the packed jquery.js and a jsmin-izied jquery-min.js: Size in bytes before gzip: 20976 jquery.js 33784 jquery-min.js Size after command line gzip: 10776 jquery.js.gz 10702 jquery-min.js.gz The compression results are a little surprising, but negligible. The difference is that javascript won't spend valuable milliseconds unpacking when your web page is first loaded. It's much faster to uncompress (native code) vs. unpack (javascript). Steve
-- Aaron Heimlich Web Developer [EMAIL PROTECTED] http://aheimlich.freepgs.com
