[wp-trac] [WordPress Trac] #11453: Use compression for CSS and JS file output

[WordPress Trac]

#11453: Use compression for CSS and JS file output
-----------------------------+----------------------------------------------
 Reporter:  micasuh          |       Owner:                              
     Type:  feature request  |      Status:  new                         
 Priority:  normal           |   Milestone:  3.0                         
Component:  Optimization     |     Version:  2.9                         
 Severity:  normal           |    Keywords:  css, js, minify, compression
-----------------------------+----------------------------------------------

Comment(by micasuh):

 Replying to [comment:8 novasource]:
 > Denis-de-Bernardy is correct about minify if it consumes a lot of CPU.
 Have to analyze on cost-benefit. At least on hosts like Dreamhost, lots of
 minify could push high volume sites into mandatory private virtual host
 mode.
 This is mostly true if visitors are downloading on-the-fly minified files.
 I don't think anyone is recommending this. While minifying files can add
 increased CPU load, if done right this increase should be very minimal.

 For minifying to be a realistic option, client-side website visitors
 should only be downloading cached CSS and JS files which have been
 minified/gzipped.

 I know there's other factors involved like someone who edits CSS and JS
 files in an external or desktop editor. I often use
 Dreamweaver/Coda/Textmate/Notepad++ to make CSS changes. Thus, when would
 Wordpress minify these files? Maybe there could be a switch to turn off
 caching and minification while a developer is coding the site which would
 again not increase CPU load.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11453#comment:9>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software