4 ms·
Advancing HTML is indeed something that the w3c members aren't super interested in. There are a few reasons for this: 1) Changes to HTML can create security is
by Touche 6y ago
Advancing HTML is indeed something that the w3c members aren't super interested in. There are a few reasons for this:
1) Changes to HTML can create security issues, especially if it results in a change to the HTML parser. You have to consider that non-browser use cases still need to be able to parse HTML correctly. Since we opted to make HTML versionless with <!doctype html> it became harder to do.
2) Big changes are harder to get consensus on. This is one of the reasons why they opt to do smaller, less controversial changes.
3) w3c and whatwg are dominated by large corporations, who hire thousands of engineers to work on their web properties. They are able to overcome the shortcomings of HTML easier than small teams and single-developer websites.
I agree though, this is a major problem. HTML is essentially a dead language, no major changes have been made in almost a decade.
- deleted 6y ago[deleted]
- WorldMaker 6y ago4) The W3C HTML spec is now mostly just a placeholder that says "Whatever WHATWG thinks is best" and it is almost but not quite true that WHATWG's Living Spec is increasingly "Whatever works in Chromium/Chrome"
- zokier 6y agoWell XHTML 2.0 was such a roaring success that I'm sure they'll be super stoked to take on another project to improve HTML as hypertext without the baggage of browser backing and buyin.
- WorldMaker 6y agoCorrect, the debate over XHTML 2.0 was exactly why the WHATWG was formed. It's indeed how the W3C lost most of its teeth in browser standards. XHTML 2.0 had some good ideas, but it shows how hard it is to govern standards from ivory towers.