4 ms·
I really wish we'd "simplify" the HTML spec. The "pave the cow paths" approach to allow non-closed tags and mix of various syntaxes has lead to an explosion of
by exabrial 9y ago
I really wish we'd "simplify" the HTML spec. The "pave the cow paths" approach to allow non-closed tags and mix of various syntaxes has lead to an explosion of complexity. That has regressed into terrible performance and memory hungry parsers.
- rhencke 9y agoThis was done once - it was called XHTML. It was, effectively, just HTML in XML form. Tags had a single syntax (no implicitly self-closing tags). Documents were required to be well-formed, syntactically, or they would not display. It did not win.
- dragonwriter 9y agoIt also didn't lose, since WHATWG HTML retains an XML syntax (no longer formally called XHTML, But it's the evolution of the same thing.) There are still use cases for the XML syntax.
- tannhaeuser 9y agoHTML had tag omission and other minimization features from day one since HTML is based on SGML which formalizes these notions. If by mix of various syntaxes you mean CSS, then I have to agree with you. There never was a need to define a new syntax for item/value pairs; plain markup attributes were and are sufficient for presentation properties.