I find this very useful...
On Oct 21, 2007, at 11:26 PM, Andrew Wyllie wrote:
> Maybe I wasn't really very clear. I don't think 'minifing' your JS/
> every time it's requested is very useful. You should either
> preprocess it
> and then install it on the webserver (in which case you would not
> need a
> mod_perl module) OR you could use a mod_perl module that minifies
> the JS/CSS code
> if it changes, caching the result to use for subsequent requests.
> It seems like
> a bit waste of cycles to minify every time the file is requested,
> and worrying
> about the speed of minification seems unnecessary.
> ----- Original Message -----
> From: "John ORourke"
> To: "modperl List"
> Sent: Sunday, October 21, 2007 12:54:12 PM (GMT-0500) America/New_York
> Subject: Re: ANNOUNCE: XS-based minifiers for JS/CSS
> If you'll pardon the devil's advocate bit...
> Caching isn't really the issue - you can use mod_cache, or make
> your own
> using CSS::Minifier. I think Bjorn was questioning the
> Apache2::Filter::Minifier:: approach.
> Here's a different take on Apache2::Filter::Minifier. I run a
> small web
> dev shop, I code perl and manage the servers, and I have a small
> team of
> web developers who make works of art using JS and CSS. I have a few
> hundred man-hours* per month for development. We're talking about
> simply deploying a module to speed up some sites, without it using up
> many man-hours. Thanks, Community!** This helps me proudly tell my
> customers about mod_perl, and in will help my business get to the
> where we can contribute code and ideas back to the community.
> * woman-hours too, of course, but it's still all blokes here
> ** Community as in Graham, Geoffrey and co
> Andrew Wyllie
> Dilex Networks, LLC