Update on parsing HTML. I initially thought of using exoml to parse HTML as well, I dismissed that idea.
Practically HTML cannot just be tokenized into a tree like XML.
HTML is its own very weird language, and cannot be treated as XML at all. They look very much the same, but are insanely different in their inner workings.
So using exoml to build a tree out of a HTML document will lead to problems.
I refer to the introduction of Alexander Borisov, the author of myhtml, explaining the tokenization/parsing issue in greater detail: http://lexborisov.github.io/benchmark-html-persers/
An HTML parser is:
Tokenizer — breaking text down into tokens
Tree Builder — placing tokens in “correct positions” in a tree
Tree follow-up
Someone out of the blue might say: “There’s no need to build a tree for HTML parsing, it’s enough to get tokens.” Unfortunately, they’re wrong.
Actually, for correct HTML tokenization, we should have a tree at hand. Points 1 and 2 go as one.
He gives a great concise example:
Example 2:
<svg><desc><style><a>The result of correct processing:
<html> <head> <body> <svg:svg> <desc:svg> <style> <-text>: <a>
That is also why I started working on Bindings for myhtml.
See this thread: Myhtmlex - bindings to lexborisov's fast html parser myhtml
