> it's still unacceptable for minification to take more than 1-2 minutes. This is something we could try fixing in the future.<p>Wow. Yes. I would even say taking more than a <i>single second</i> is pretty unacceptable. There's a bad algorithm in there somewhere...
The workarounds to handle client-side templating seem dirty. Is it really true that e.g. Handlebars requires you to send illegal HTML to the browser? That seems like such a bad idea.
I'd love your feedback on a similar Rack middleware for Rails: <a href="https://gist.github.com/frankie-loves-jesus/d7eec0ebab0525e94256" rel="nofollow">https://gist.github.com/frankie-loves-jesus/d7eec0ebab0525e9...</a><p>To me it's mainly for cosmetic purposes -- partly because Google does it and I want to be like Google -- and because I want to give a little "fuck you" to my competitors who will inevitably try to read my source.
Kangax: Just one notice, it chokes on comments like this:<p>/<i></i>*<p>* _ _<p>* | (_)<p>* __| |_ ___<p>* / _` | |/ _ \<p>* | (_| | | __/<p>* \__,_|_|\___|<p>*<p>*/<p>No biggie, but had to manually remove them from my code.
I prefer a HTML minifier that parses and builds in internal AST (like Google closures compiler for JS) over a regex-based minifier.<p>HTML-minifier seems like a good solution, thanks, will try it out.
I really would like to see a comparison of the minified + gzipped vs just gzipped vs just collapsing all multiple blank spaces into a single ones + gzipped