I can write an XHTML1.1 parser and renderer in about one month.
Writing an HTML5 parser takes thousands of developers 5 years.
You are comparing two things that aren't equivalent. The living standard provides a lot more value than the old specs, and that's why they won.
We’ve made parsing the web something that only massive corporations can do. We’ve made building a browser so complicated that even Opera gave up after the complexity of HTML5, and we’re now left with only 4 major browser engines, of which 2 share a significant amount of code.
Do you see an innovative ecosystem there?
We’re left with a web that can’t be parsed, we’re left with a web where, to run Selenium tests, we have to run Chrome headless, because nothing else can even attempt to render websites anymore.
Yes! Everyone says that the specification approach is what was severely limiting innovation, and when they took the living specification approach instead that's when web innovation took off again.
Every tool we have to use on the web relies on 4 existing tools that only major companies can build.
I’ll pay you $100 if you manage to write, in 4 weeks, a browser, from scratch, that renders a real life React app accurately, including all content, without importing a single bit of code or libraries from existing browsers or web tools.
I don't recall XHTML deprecating JavaScript- pray tell, how would you render the XHTML version of a react app without a browser, or a JS engine as a bare minimum? (X)HTML is orthogonal to Js/react.
I could develop a self-driving car for $50 000 (instead of millions) if human drivers and pedestrians started behaving in well-defined patterns, following strict rules and stopped doing stupid, unexpected things. I'd really love that, but it's not going to happen even though there already are "standards" in the law books.
I don’t want more powerful ways to display ads, I want to get more content, better connected, without any of the fluff around it.
I don't care directly about competition, because that's just a means to an end, and the end I care about is innovation, and I don't agree that innovation is low - I think it's high. New HTML features are coming out in a fast continuous stream, unlike how it used to be.
And yet, that’s where we’re at today. Blogspot posts require JS. So many other pieces of content are similarily built.
And with phatomjs gone, we’re now running entire headless browsers just to test if websites are rendered correctly. It’s insanity.
Then you need to take that `.exe` and try and pull out it's content. Game, app, whatever.
We have a web that can be parsed, with difficulty, instead of a web without half of the content we want to parse.
The web was being replaced - this is what saved it, like it or not.
This is demonstrably untrue. Servo's HTML5 parser, html5ever, was largely written by a single developer within a year. (Yes, it's not a month, but it's also not 5 years.)
I believe it would have been. And I believe that making the web easier machine readable, and making it easier for people to develop tools working with the web, would be a valuable goal.
Not really.
> Wouldn’t it have been easier if the syntax was formally defined as ABNF, and could be translated into code in a matter of days?
No, working from an spec written as an algorithm is easier than working from ABNF plus some inconvenient prose constraints.
(With the exception of template element support, I wrote the HTML parser used in Firefox and Validator.nu.)
That sounds very unlikely.
I’ve implemented my own parsers for countless specs – plaintext or binary, and the parsers that are written as imperative algorithms are insanely complicated to implement as functional implementations.
I end up with horrifying code, while the specs written as ABNF are much easier to translate into pattern matching code.
The specs written as algorithm only work fine for a single type of implementation IME, while the ABNF specs work equally well for all types.
Why do other actors need to rely on the W3C? Why can't they use the WHATWG specs as well? You say they're more complicated, but if that's what the browsers do then that's what they do.