Posted by: Arthur Blake | 2009-08-09

CompressorRater 1.0.9 updates

With this release, I’ve updated the Packer compressor from 3.1 alpha 3 to 3.1 final. The Packer compressor with spidermonkey continues to be some 20x times faster than the rhino based version, making the compressorrater all that more easy to use as a your go to javascript compressor.

About these ads

Responses

  1. The table column labelled “Run Time” is, I assume, the time taken to *compress* the JavaScript. It would be very useful to know browser *decompression* time. It’s important to be aware of the impact of eval (de)compressors as they may well slow rather than increase page load speed (especially on slow or handheld hardware).

  2. Yeah, that would be nice. I am however thinking about disabling base64 compression by default (the ONLY runtime decompression in the current mix) as I don’t think runtime decompression is really very valuable these days.

    With gzip (technically gzip is a runtime decompressor too, but it runs in native code in the browser and it’s so fast that it doesn’t count) and a decent minification+shrinker the compressed results are usually only a few hundred bytes different… IMO not worth the extra overhead of a run time decompressor.

    The only good reason I can think of using a runtime decompressor is for obfuscation, but it’s so easy to get around that, it’s not even funny… and minification+shrinking obfuscates pretty well against casual observers anyway.

  3. I have make another javascript compressor called JSXS :

    http://www.xorax.info/labs/jsxs/

    It’s a minimifier like YUI Compressor with some other features.

    Just try it and give me your feedback :)

  4. Is Closure ever going to be added to the list of compressors?

  5. Hi, thanx for your usefull tool. I would like to ask, if Google Closure Compiler will be added soon?

  6. Google Closure looks pretty cool. Maybe I’ll add it when I get some time.

    • I would be great to compare Closure wit YUI, especially with gzip. Even jQuery started to build minified version using Closure.

    • Me too +1 for adding Google Closure. :)

  7. +1 on adding Google Closure Compiler to the mix.

  8. I recommend this tool to everyone but with an enormous disclaimer…. which is that it doesnt come with Closure Compiler.
    It needs to.

    Also Dean Edwards himself would recommend against using the base62 encode with packer, so I think that option should be disabled.

    • Thanks. I agree about base62 (as I mentioned earlier in this thread and elsewhere) I may remove that option from the defaults.

      As for Google closure, I plan to add that when I can. This project is something I work on in my spare time… and there isn’t much of that!

  9. Hey Arthur

    Thanks so much for CompressorRater. What an excellent tool! You should put up a Donate button so that people can contribute to your great work.

    Best Regards
    Gavin

  10. Hey Arthur!

    Nice, your comparison tool is #1 on Google when I search “JavaScript compressor”. :-) Do you still maintain it?

    I wrote a JavaScript compressor which beats YUI Compressor and it’s close to Google Closure (sometimes better) in terms of output code size. And it’s faster than both (by far). :-) It would be neat if you could include it as an option in your comparison tool. JQuery is planning to switch to it starting next version.

    Here’s the tool: http://github.com/mishoo/UglifyJS (it’s for NodeJS) and here you can try it online: http://marijnhaverbeke.nl/uglifyjs

    Cheers,
    -Mihai

    • I do plan to update the compressorrater at some point- I’ve already started to add Google Closure to the mix, but I’ve just been too busy with other projects to work on it lately. I’ve followed your UglifyJS project on github– it looks like a nice compressor. I may add it later as well.

    • +1 for UglifyJS

      I’ve also been following the UglifyJS project, and I’ve had a great experience using it :)
      Almost always I get better compression rates than other minifiers.
      And on one occasion Closure was breaking my code (when using advanced optimizations), while UglifyJS worked perfectly and even produced a smaller result :) how about that ? :)

      Keep up the good work, both of you

      • Thanks for the comment. I used to spend a lot of time to try and obtain compression nirvana and eke out those last few bytes of compression, but more lately I’ve taken a more practical approach.

        JSMin tends to be by far the fastest compressor, so it can often be used on demand in realtime while serving pages, and once you add gzip it’s almost always very close in compression levels to the more sophisticated but slower compressors.

        I still would like to add closure and UglifyJS to the mix whenever I can get my head above the water on current projects.

  11. It would be extremely nice to Google Closure Compiler and UglifyJS added to the list of compressors here.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: