4 ms·
Note that this is not the WHATWG standard that all browsers follow. https://news.ycombinator.com/item?id=12848419 https://news.ycombinator.com/item?id=12848419
by bryanlarsen 10y ago
Note that this is not the WHATWG standard that all browsers follow.
https://news.ycombinator.com/item?id=12848419 https://news.ycombinator.com/item?id=12848419
- Waterluvian 10y agoWhat is W3C doing here then? Or will what WHATWG standardizes will basically be what this is?
- TazeTSchnitzel 10y agoThe W3C standard shall be a plagiarised, outdated, incomplete copy of the current WHATWG standard forevermore.
- wrs 10y agoSee https://html.spec.whatwg.org/multipage/introduction.html#history-2 https://html.spec.whatwg.org/multipage/introduction.html#his... >In 2011, however, the groups came to the conclusion that they had different goals: the W3C wanted to publish a "finished" version of "HTML5", while the WHATWG wanted to continue working on a Living Standard for HTML, continuously maintaining the specification rather than freezing it in a state with known problems, and adding new features as needed to evolve the platform. >Since then, the WHATWG has been working on this specification (amongst others), and the W3C has been copying fixes made by the WHATWG into their fork of the document (which also has other changes).
- wolfgke 10y agoThis excerpt is a good summary of the smugness that I hate the WHATWG for.
- mwfunk 10y agoWhat in that excerpt conveys smugness to you?
- wolfgke 10y ago* the W3C wanted to publish a "finished" version of "HTML5" Putting "finsished" into quotes is a hint of sarcasm of the WHATWG side. * continuously maintaining the specification Fixing known bugs is also a kind of continuous maintaining of a standard (this is what the W3C and other standard bodies do). That the WHATWG writers put this into contrast of the approach of the W3C is smugness again. * rather than freezing it in a state with known problems Fixing bugs and publishing errata is common for standards. The wording implies that this is something the W3C does not do. * and adding new features as needed to evolve the platform Having a stable standard which one can refer to (say in project contracts or for tooling) is also an important feature. The WHATWG connives over this and only considers the things that they do as features. * Since then, the WHATWG has been working on this specification (amongst others), and the W3C has been copying fixes made by the WHATWG into their fork of the document A very smug way to say "WHATWG does all the work and W3C is a copycat". Though the facts might be true, there are more humble ways to express that. * (which also has other changes). OK, what the W3C does is not really important - we can skip over these changes as they are not important (only the WHATWG version is).
- gsnedders 10y agoRe: > Fixing known bugs is also a kind of continuous maintaining of a standard (this is what the W3C and other standard bodies do). And: > Fixing bugs and publishing errata is common for standards. The wording implies that this is something the W3C does not do. There are countless W3C specs that don't have errata kept up-to-date, and, hell, the 5.1 errata is just <https://github.com/w3c/html/issues> https://github.com/w3c/html/issues> (if they fix a bug in 5.2 drafts, will they keep the issue open so it continues to appear on that (paginated) list of issues or not? because both options seem terrible!). Similarly, the W3C almost never issues revised recommendations to incorporate errata, which means even for specs where there have been no errata for years you have to cross-reference two documents. Another example is CSS 2.1, which doesn't have errata published any more: they're just fixed in the editor's draft of 2.2, and left to linger in the 2.1 Recommendation and errata. For plenty of W3C specs the only "errata" is an editor's draft of the next revision.
- Esau 10y agoI'm not seeing that. Can you elaborate?
- unethical_ban 10y agoVersioned != stale. A proper standards group could have a new HTML x.Y version come out every 6-12 months. Now, who knows what is valid HTML? I don't know where to go to know when or if a <date> or <number> or <em> or <marquee> tag is valid, or what browser supports it.
- dfabulich 10y agoThere was a good discussion of this on HN when HTML 5.1 was announced as a W3C Recommendation, 16 days ago. https://news.ycombinator.com/item?id=12848419 https://news.ycombinator.com/item?id=12848419