4 ms·
The parser. Once for properly parsing HTML content, for a search engine, and the other for a framework used for saving pages (For an Instapaper like service). S
by markpapadakis 9y ago
The parser. Once for properly parsing HTML content, for a search engine, and the other for a framework used for saving pages (For an Instapaper like service). So it wasn't a big deal, but in both cases, a DOM was constructed and operations were executed against the DOM.
Nothing about that or the JS engine is impressive really. That was my point, more or less. Of course, there's a difference between building something that works, and something that works exceptionally works etc etc(all the stuff on top of that), but all told, I still don't think building a browser justifies assembling such a huge org, even if there is no reliance on third-party technologies.
- chrismorgan 9y agoImplementing an HTML parser is not hard—the spec is a book of instructions on what to do. Implementing a fast HTML parser that will produce a fast DOM is a little harder. Tying it in with a fast CSS engine is harder still. Tying it in with a JavaScript engine is a bit more work as well. Implementing layout is moderately fiendishly difficult to do and get right. And it just gets harder the more of the web platform you add, and the more it has to be fast.
- roca 9y agoHTML5 parsing is maybe 1% of the HTML5 spec.