Re:The HTML5 Parsing Algorithm
by tedunangst on Friday August 06, 2010 @12:37AM
(#1580209)
Addition is simpler than combination.
[ Parent
| on HN ]
They're extremely similar. You don't get an explosion of code size. Unless you're suggesting that HTML5 should also be radically different syntactically as well?
Re:The HTML5 Parsing Algorithm
by tedunangst on Friday August 06, 2010 @11:48AM
(#1581338)
I'm suggesting that a strict HTML5 parser that doesn't have complex recovery code is radically simpler than one that does.
I'm suggesting that a HTML4 parser that has complex recovery code, and a mostly-copy-and-paste HTML5 parser that doesn't isn't a big win.
Browsers are going to have a complex, ugly, recovery-enabled parser in them either way, and the effort to add HTML5 to the recovery-enabled parser isn't very big, comparatively speaking.
Re:The HTML5 Parsing Algorithm
by othermaciej on Friday August 06, 2010 @05:19AM
(#1580604)
Not really true in this case. WebKit's previous HTML parser is similar in complexity to the HTML5 parser. Adding a second HTML parser would have been more code, more complexity, and a more complex test matrix.
Complexity does not increase linearly with number of lines of code. 110k lines can easly be 5x as complex as 100k lines of code.