Comment by jraph
3 hours ago
> It will leave you yearning for the return of XHTML.
…or be grateful you can just use an existing HTML5 parser that hides all this stuff to your innocent eyes :-)
3 hours ago
> It will leave you yearning for the return of XHTML.
…or be grateful you can just use an existing HTML5 parser that hides all this stuff to your innocent eyes :-)
Grateful in part, but I can't help to think that if there was refusal to build parsers for an outlandish spec in the first place then we'd have fixed the problem by now.
Using existing parsers only hides the poor design up to a point.
I'm conflicted on this.
I mostly agree with the sentiment, I'd rather have simple parsers and sensible specs, but I'm also happy they do whatever it takes not to break anything (well, they are breaking XSLT…)
Nowadays you can use AI to write the parser, so it's the machine the one that suffers I guess.
https://friendlybit.com/python/writing-justhtml-with-coding-...