I hope that in determining which HTML is optimal bandwidith wise, there is also some consideration of what HTML is optimal rendering wise. (obvious cost savings of going hard down the bandwith optimizing aside) Knowing how the parser treats certain constructs and deviations from the spec. probably gives us some insight into how long things will take to parse. Or is client side that much faster than waiting on normal…
The parsing time is probably negligible. I would guess that parsing HTML5 would be a few if not dozens of megabytes per second on modern hardware.
Mathematically optimal markup with HTML5
11–20 of 28 posts
Re: Mathematically optimal markup with HTML5
#12Does anyone have more details or examples of Google's "crige-worthy" HTML for efficiency?
Go view the source of Google.com No or tags for one.
Re: Mathematically optimal markup with HTML5
#13I hope that in determining which HTML is optimal bandwidith wise, there is also some consideration of what HTML is optimal rendering wise. (obvious cost savings of going hard down the bandwith optimizing aside) Knowing how the parser treats certain constructs and deviations from the spec. probably gives us some insight into how long things will take to parse. Or is client side that much faster than waiting on normal…
Re: Mathematically optimal markup with HTML5
#14Earlier quoted context omitted.
The parsing time is probably negligible. I would guess that parsing HTML5 would be a few if not dozens of megabytes per second on modern hardware.
Parsing speed depends on the markup. One example is text layout, which is O(N) in the size of the text area. So 1 MB of text might be a lot slower to parse than 1 MB of no-op tags.
Re: Mathematically optimal markup with HTML5
#15Re: Mathematically optimal markup with HTML5
#16I love how the author uses omitted- as their example, when that's one of the things that was actually already defined in HTML4 and isn't a syntax error.
Re: Mathematically optimal markup with HTML5
#17I hope that in determining which HTML is optimal bandwidith wise, there is also some consideration of what HTML is optimal rendering wise. (obvious cost savings of going hard down the bandwith optimizing aside) Knowing how the parser treats certain constructs and deviations from the spec. probably gives us some insight into how long things will take to parse. Or is client side that much faster than waiting on normal…
I'm curious if we will see actual packers that rename tags and rewrite css to drop markup size. HTML5 seems to make it easier to create your own tag soup. :)
Re: Mathematically optimal markup with HTML5
#18Does anyone have more details or examples of Google's "crige-worthy" HTML for efficiency?
Go view the source of Google.com No or tags for one.