3 ms·
You see this concern about file size of websites all the time, but the extra white space is not what makes websites large, it’s all the images, fonts, and JavaS
by _mlbt 3y ago
You see this concern about file size of websites all the time, but the extra white space is not what makes websites large, it’s all the images, fonts, and JavaScript libraries that get bundled with them. For most sites the HTML is negligible and compresses well if you enable GZip.
- chrisweekly 3y agoTrue. Also, for a typical web page, over 90% of user-perceived latency occurs AFTER the HTML has been fetched, unzipped, and parsed. That doesn't mean minification and compression are worthless, but it may help put things in perspective.
- cantSpellSober 3y agoYep, I know images are big, fonts are evil and what gzip is. Instead of "why not?" the author could sell the "why" there.
- djbusby 3y agoSoon as I saw the title I thought their "why" was: so it looks good when I view source.
- cantSpellSober 3y ago"why" in the repo, not the HN title
- jkestner 3y agoI'd say, it's to optimize for source readability. That's something many of us relied on to learn HTML, and we need to keep that path open.
- dinkleberg 3y agoNot everything in life needs to be optimized.
- pfarrell 3y agoAnd not every optimization is worth the effort.
- cantSpellSober 3y agoIn this case effort was required to remove the optimization.
- cantSpellSober 3y agoNope! We weren't talking about "everything in life" but instead HTML in statically-generated websites.