3 ms·
The savings is marginal, but if you are able to set it up once and forget it, why not take advantage of a few % reduction in page size?
by bobblywobbles 8y ago
The savings is marginal, but if you are able to set it up once and forget it, why not take advantage of a few % reduction in page size?
- fiddlerwoaroof 8y agoWell, for one thing, minification makes debugging production issues needlessly difficult.
- bobblywobbles 8y agoThat might be the case for javascript or css, however even if the HTML is sent down minified, the browser will not show this minified HTML if you and Inspect it. Was there a specific case you were referring to?
- GordonS 8y agoBecause it adds complexity to the build process, for very little benefit. And I don't like complexity. To illustrate the point, let's take the current Hacker News front page: +=================+========+ | Description | Bytes | +=================+========+ | Original | 43,595 | +-----------------+--------+ | Minified | 41,368 | +-----------------+--------+ | Original (GZIP) | 7,350 | +-----------------+--------+ | Minified (GZIP) | 7,247 | +-----------------+--------+ You've saved 103 bytes, or ~1.4%.
- bobblywobbles 8y agoThat's true, but if you need that extra benefit then it's worth the cost. As long as the process is invisible for you once you set it up, would you justify the complexity for extra gain?
- GordonS 8y agoPersonally, not for such a tiny saving - and it's only invisible until it stops working "because NPM", and needs tinkering with to get working.