News for hackers. Stuff that matters.
Re:Ask YC: Any risks with JS and CSS compression? by qhoxie on Tuesday August 26, 2008 @03:12AM (#286837)
There aren't really any risks involved aside from the fact that most (all?) compressors expect well-formed scripts, and thus can break ones that don't meet standards.

A common way to do compression that will give you a similar effect is to gzip content from the web server.

Re:Ask YC: Any risks with JS and CSS compression? by prashantdesale on Tuesday August 26, 2008 @03:23AM (#286852)
Thanks a lot.
Re:Ask YC: Any risks with JS and CSS compression? by nostrademons on Tuesday August 26, 2008 @09:37AM (#287047)
In particular, most compressors are picky about semicolons. If you use JavaScript's implicit line breaking, they'll break. This includes function definitions: there should be a semicolon after each function definition, something that most JavaScript programmers forget.

I find that using JSMin + GZip (on the webserver level) compresses just as well and tends to break fewer things.