Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Does anyone know why XHTML failed? I remember deriving some satisfaction from making my website XHTML compliant back in the day.

Wouldn't it make it much easier to parse? Or does the motivation to "make stuff still try to work even when it's clearly broken" override that? (The same motivation gave us everything that's wrong with JavaScript, so I'm not sure I agree with it...)



XHTML was not backwards compatible and was harder to write for essentially no benefit to most people. "It's XML" was basically the entire list of selling points, and that was just not a compelling enough proposition — in fact, for many people, that was negative value.


> XHTML was not backwards compatible

Sure?

I think it was HTML4 that was not forwards compatible.

XML is a subset of SGML, and HTML4 was SGML. XHTML was / is XML. So HTML4 parsers (as being SGML parsers) shouldn't have issues with XHTML.

It's the other way around: XML parsers don't like HTML. So the attempt failed to change the default parsers to XML; as old webpages had than issues, and the web crowd didn't like to fix that. People wanted to continue to use the horrible SGML mess—only because nobody wanted to touch their HTML4.

So Google created their own web "standards council" and ignored the W3C henceforth. The rest is history.


You can still write HTML in XML syntax. It's not wrong afaik.

But HTML can be also written in some absolute quirky way that isn't even SGML. Just a horrible mess!




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: