Re: experiments with closure compiler

[Paul Lindner <li...@inuus.com>]

PHP is still using jsmin...

On Wed, Jan 20, 2010 at 7:49 AM, Tim Wintle <ti...@teamrubber.com>wrote:

> On Tue, 2010-01-12 at 17:19 -0800, ๏̯͡๏ Jasvir Nagra wrote:
> > YUI compressor compresses all valid input javascript correctly.  Closure
> > compiler under simple mode accepts a subset of javascript and produces
> > output that tries to be compatible with Caja's output semantics (
> > http://code.google.com/closure/compiler/faq.html#caja).  If we are
> willing
> > to author in a subset of javascript, we should instead aim for the Caja
> > subset (specifically the cajita subset).  The Caja Web Tools package (
> >
> http://code.google.com/p/google-caja/source/browse/#svn/trunk/src/com/google/caja/ancillary/opt
> )
> > provides comparable compression as well as a linter and jsdoc tool.  The
> > significant advantage over targetting closure compiler would be the
> ability
> > to inline gadgets on a page instead of iframing them.
>
> I hadn't come across the compiler in caja (I haven't really looked at
> caja) - but isn't a major benefit of the Closure compiler supposed to be
> optimised runtime?
>
> Just interested how that is/isn't included in the caja tools.
>
> Also, what's the state of the PHP javascript compression? IIRC the PHP
> version is/was stuck with jsmin (or off-line compression during
> deployment).
>
> Tim Wintle
>
>