3 ms·
Like many other commenters have said, it makes a lot more sense to have this in a build step rather than doing by hand -- there's a lot of somewhat arbitrary ru
by yladiz 10y ago
Like many other commenters have said, it makes a lot more sense to have this in a build step rather than doing by hand -- there's a lot of somewhat arbitrary rules (see when you can omit a "p" closing tag for example) that can be explicitly handled during building.
However, what does this really accomplish? Does it really save that much space and bandwidth? GZIP compresses text extremely well, so I don't see the usefulness in most cases. Sure, for really slow networks, e.g. in developing countries, it might matter, but the people that this guideline are targeting are likely not going to worry about that. Maybe at Google scale it makes a difference.
Beyond that, it really feels weird to omit the html tag and the head tags and I'd like to see how much more readable this optional tag omission is when you're dealing with a complex page with many meta tags and a ton of body content.
- mbrock 10y agoI've been omitting needless tags since HTML5 became a thing and I'm totally over any residual "weird feelings" from the XHTML days.
- markdown 10y ago> Sure, for really slow networks, e.g. in developing countries, it might matter, #thirdworldproblems, eh? There are more third-worlders than there are visually impaired people. Do you also disregard the blind?
- elmigranto 10y ago> Does it really save that much space and bandwidth? I would think on Google scale saving a byte is like couple hundred dollars or some other non-trivial amount (but at same google scale this is pennies). Then again, if Google homepage is 5 bytes less, gigabytes will be saved delaying heat death of the universe or something… :)