Quote:
Originally Posted by KevinH
The answer is no, there is no appreciable code loading or execution differences 99% of the time.
And an epub publisher who uses a standard css across a number of books, is much more likely to make fewer errors of omission or design, thus improving quality.
JSWolf has simply overstated/over claimed things as usual. He makes unneeded changes for no valid reason other than he thinks it should be so and gets irrationally upset when explained otherwise.
Making code simpler when possible is always a good thing, but simplifying classes when css inheritance is in effect (and with some css injected by the reader) itself is fraught with errors and really is not a good idea.
Removing unused id attributes is another one of those short sighted mistakes people make as external cfi references by scholars and others into locations inside the epub, page boundaries, and etc are often lost or destroyed.
And as a practical rule, anything that does not significantly impact loading or execution speed should generally be left alone is probably a good idea.
What JSWolf does with his own books is up to him, but advocating his views to everyone else as a "law" is not. Simpler is better until it is not. Be careful making changes not fully understood. Adding or removing default css from a class can and does impact inheritance and can cause errors when reader injected css exists that needs to be overridden, etc.
|
Thank you. In my case, he did tell me "Your ID's do nothing so you don't need them." when I posted a snippet from my code, even if I did need at least one of them for the index to work.