Re:Google to restrict modern ad blocking Chrome extensions t...
by dredmorbius on Thursday May 30, 2019 @01:49AM
(#20048737)
XHTML was a step too far. It was rejected in favour of HTML4 & 5, ultimately.
[ Parent
| on HN ]
Re:Google to restrict modern ad blocking Chrome extensions t...
by ori_b on Thursday May 30, 2019 @12:47PM
(#20053164)
xhtml seems to me quite a bit simpler to implement than HTML5.
Re:Google to restrict modern ad blocking Chrome extensions t...
by dredmorbius on Thursday May 30, 2019 @01:37PM
(#20053810)
XHTML is hard-structured, and among its negatives, requires being fully downloaded to be parsed and validated.
HTML, including H5, has soft-fail modes.
At least that's the justification I generally see. See the Criticism section of the Wikipedia article:
Re:Google to restrict modern ad blocking Chrome extensions t...
by ori_b on Thursday May 30, 2019 @03:51PM
(#20055244)
That makes HTML5 harder to implement, not simpler.
Re:Google to restrict modern ad blocking Chrome extensions t...
by dredmorbius on Thursday May 30, 2019 @04:15PM
(#20055459)
HTML5 != XHTML. (If that's what you're saying.)
HTML5 breaks soft. It's easier to write, which is what drives content. A parser for which there is no content becomes moot.
(I'd prefer far more rigorous document specification. That's not the Universe I inhabit.)
Re:Google to restrict modern ad blocking Chrome extensions t...
by ori_b on Thursday May 30, 2019 @04:24PM
(#20055535)
You're responding to a thread pointing out that browsers are too complicated to implement, which has forced everyone but Google and Mozilla to give up on providing browsers and web standards.
And Google is currently the funding source for Mozilla, giving them a more or less complete monopoly on the future of the web.