News for hackers. Stuff that matters.

A comment on What CSS minifiers also leave behind. Parent comment

Re:What CSS minifiers also leave behind by ricardobeat on Wednesday April 05, 2017 @07:21AM (#14041238)
Most of the gains in there are from stripping out comments. That plus whitespace removal gets you most of the benefit. I don't think the parent was advocating for dropping minification completely, but investing massive effort when you're already at the crest of the curve.
[ Parent | on HN ]
Re:What CSS minifiers also leave behind by diamondo25 on Wednesday April 05, 2017 @10:40AM (#14042389)
Stripping out comments would be one, but eventually remove all useless code and optimizing it using tools like Google Closure Compiler is way more effective in most websites that use a single bundle for everything.
[ Parent | on HN ]
Re:What CSS minifiers also leave behind by ricardobeat on Wednesday April 05, 2017 @10:50AM (#14042462)
When the subject is CSS, dead code removal is a way more complex problem, and only possible if your usage falls within certain constraints. Best bet is a component system with scopes styles that ensures you are only loading what is required.
[ Parent | on HN ]
Re:What CSS minifiers also leave behind by Klathmon on Wednesday April 05, 2017 @08:02AM (#14041418)
It's not like this is a zero sum game.

Attempts at improvement don't hurt at all, and in some cases can help a ton.

[ Parent | on HN ]
Re:What CSS minifiers also leave behind by iainmerrick on Wednesday April 05, 2017 @12:27PM (#14043284)
But they can hurt sometimes -- not all optimizations are always safe.
[ Parent | on HN ]
Re:What CSS minifiers also leave behind by Klathmon on Wednesday April 05, 2017 @12:31PM (#14043314)
Of course, but there is still value in "unsafe optimizations" for those who won't be impacted by them.
[ Parent | on HN ]