View Single Post
Old 02-06-2024, 12:23 PM   #85
nabsltd
Fanatic
nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.nabsltd ought to be getting tired of karma fortunes by now.
 
Posts: 524
Karma: 8500000
Join Date: Aug 2013
Location: Hamden, CT
Device: Kindle Paperwhite (11th gen), Scribe, Kindle 4 Touch
Quote:
Originally Posted by JSWolf View Post
Otherwise, you have code bloat. <p> is even worse as you'll have severe code bloat with <p class="codebloat">.
This is not a problem.

In my library, a 188,000 word EPUB with <p class="para-indent"> is 829,165 bytes. In that EPUB, there are 6,207 p elements with that classname. Changing it to just <p> shrinks the EPUB to 824,776 bytes, a miniscule savings of 4,389 bytes, or less than 1 byte per paragraph.

To put it another way, on a device with 32GB of storage, the you could hold 38,593 "bloated" books, but only 205 more if you remove the "bloat". The use of a meaningful class name far outweighs the space savings.

And, it doesn't really matter how long the class name is. Changing to <p class="ThisIsFarTooLongAClassNameToType"> increases the overall size to 833,321. This is an increase of less than 1 byte per paragraph, and it's a ridiculously long class name that would never be used for real.

OTOH, removing the cover saves 336,714 bytes. That's a lot more "bloat" than anything caused by the HTML and CSS markup.
nabsltd is offline   Reply With Quote