Re:Forking HTML into a static language doesn't make sense
by sergeykish on Monday June 22, 2020 @04:43PM
(#23606347)
XHTML was not that bad. It was quite conservative - make serialization/deserialization idempotent, remove document.write, quirks mode, DOM Level 0 accessors.
The stupid part was advertising of writing XML by hand - both XHTML and XSLT. That is machine format - "application" in "application/xml". Not more sense than writing JS AST. And semantic web has no advantage for author.
XHTML 2.0 - XML Events is like IE <script for>, <img>alt</img> is good, <h> is good, removal of <i>, <b> - no one would see, XForms - partly adopted, and RDF - don't know.
Though it kind of understandable - XML was in rage. Everyone pushed it, Microsoft above all, IE5 accepted "text/xml" [1]. And Microsoft pushed XSLT without XSL-FO.
Re:Forking HTML into a static language doesn't make sense
by recursivedoubts on Monday June 22, 2020 @03:27PM
(#23604994)
thank you for clarifying
i knew there was some drama betweeen the two organziations but didn't know the history
W3C isn't interested in advancing HTML as anything and, even if they were, they'd be screaming into the night because none of the people who build browsers are interested in what they have to say. They’ve got their own club, and that's where HTML happens (and WHATWG and the browser vendors don't seem to be interested in pushing functionality into HTML in any big way, they are happy with the basic shape of the existing HTML/CS/JS trinity and don't see a big need to push for standalone HTML as a platform.)