My Comment in Response to the Latest News from the W3C

by The H.E.A.T. Exchange

A new blog post was published on the W3C’s website today (28 May 2019). The post speaks about a collaboration between the W3C and the WHATWG. On the surface, this sounds like great news, but the surface has already been torn asunder from past disagreements between the two organizations.

The results of this “war” has been two separate camps: one that supports HTML 5 and one that supports HTML Living Standard.

The real problem, though, is that no winner has come forth from this war. No. We have two specifications covering HTML, but neither one based on any standard. The two specifications are basically opinions and ideas forged together to appear legitimate, but unenforceable and irrelevant to implementers.

There is so much disagreement between the implementations of these [HTML] specifications in browsers, assistive technologies, and Web Ds (designers, developers, and douchebags) that developing a single core specification that is based on the strictest of standards is of paramount importance.

H.E.A.T.

I commented on the blog post by the W3C, but I expect my comment will not survive there. Therefore, I will publish my comment here to keep everybody honest.

If I said I didn’t see this coming, I would be lying.

A CONSORTIUM handing over the reigns to the development of a core set of specifications to a renegade WORKING GROUP.

Much like in high school, the NERDs of the W3C have decided to subjugate themselves to the JOCKs of the WHATWG.

Use any amount of fancy wording and explanations you can dream up. The simple fact is the W3C has just kowtowed to a working group that has little to no respect for the W3C.

The fact that HTML 5.2 allows for heading elements (H1 – H6), which implies sections, inside a LEGEND element is demonstrative of what happens when you build something that is not based on a standard.

“The W3C mission is to LEAD the World Wide Web to its full potential by developing protocols and guidelines…”

I capitalized the word Lead because turning over development of the core specifications to a bunch of renegades bullying their way into acceptance is not leading.

The boss doing the secretary’s work is not leading. The parent allowing the crying fat baby to eat cookies is not leading.

A consortium allowing a working group that disrespected it every step of the way is not leading.

It’s simply being subjugated. Call it what you like.

H.E.A.T.’s comment posted on the W3C Blog on 28 May 2019