5 ms·
Full story here: https://www.reddit.com/r/javascript/comments/5swe9b/what_is_the_difference_between_the_w3c_and_the/ddkwft4/ https://www.reddit.com/r/javascript
by dmitriid 9y ago
Full story here: https://www.reddit.com/r/javascript/comments/5swe9b/what_is_the_difference_between_the_w3c_and_the/ddkwft4/ https://www.reddit.com/r/javascript/comments/5swe9b/what_is_...
tl;dr: Ignore w3c's HTML "standards" as they are (often poor) copies of WHATWG's standards.
- jcrben 9y agoDomenic Denicola posted similar thoughts on Stackoverflow as well: https://stackoverflow.com/a/43082734/4200039 https://stackoverflow.com/a/43082734/4200039
- dmitriid 9y agoYeah, that's him both on SO and Reddit :)
- wolfgke 9y ago> WHATWG's standards I my opinion one cannot call something a "standard" that changes every few days. EDIT: In this sense W3C's HTML 5.x can be considered a rather badly authored (cf. other comments here) standard, while what the WHATWG releases is not something that even measures up to a standard, but it is the daily version of how HTML is supposed to be today.
- andrewmcwatters 9y agoExactly. How the hell is someone supposed to built against their work? You can't, it would just be piecemealed.
- Touche 9y agoJust because something changes often doesn't mean it is unstable. Do you ever shop at amazon.com? I do, and I find it pretty stable. Just because it changes often doesn't mean things are sloppily accepted, or that experimental ideas are added and later removed. Indeed, if you want to build something for the web, reading an outdated document that contains bugs browsers have already fixed is not a good idea.
- wolfgke 9y ago> Just because something changes often doesn't mean it is unstable. When you do a project contract, you surely want to define the exact standard with respect to which the application is to be developed against, so that one can decide whether the reason for something looking wrong is a browser bug (I can work around it - but it will cost extra money) or indeed a bug in my code that the customer found (i.e. I have to work extra hours for no money because I did bad work). To be able to decide such questions is a central purpose of existence for standards.
- Touche 9y agoWhen I do a project I want to be able to code against the standards from which browsers were developed; that is the WHATWG standard.
- wolfgke 9y ago> When I do a project I want to be able to code against the standards from which browsers were developed; that is the WHATWG standard. I already argued that there is no WHATWG standard, but only a document that changes every few days. Even without this nitpicking: Which of these thousands of versions is the one on which the browser implementation is based on?
- Touche 9y agoThis one: https://html.spec.whatwg.org/multipage/ https://html.spec.whatwg.org/multipage/ . Contrary to some people's perception here, everything that goes into this is implemented by at least 2 browsers.
- xg15 9y agoAgain, which one? The one from November 14, 2017, the one from December 14, 2017 or the one from January 14, 2018? Do you really want to make a requirements document that describes something different at the day you sign it and at the day you deliver?
- LaGrange 9y agoIt's not enough to be stable to be a standard, you also need authority that enforces it. Either because people "respect you" (whatever that means), or because there's a central authority forcing them to implement the standard, people actually implement it. If they don't, then it's not much of a standard. So, WHATWG is in constant flux, and W3C has about as much authority as I do. _Thankfully_ in practice WHATWG is "stable enough," but just saying that's what "we" consider a good enough standard for something used in creating all sorts of UIs, from trivial to vitally important, is indicative of a bigger problem.
- dmitriid 9y agohttps://github.com/whatwg/html/blob/master/FAQ.md https://github.com/whatwg/html/blob/master/FAQ.md What parts of the standard are stable? The whole standard is more or less stable. There are some parts of it that describe new technologies that have not yet been implemented everywhere, but at this point those additions are only added after the design itself is pretty stable. Such additions must also have the support of two or more implementers, per our working mode[1]. Why are there no stable snapshots, or versions, of the standard? In practice, implementations all follow the latest standard anyway, not so-called "finished" snapshots. The problem with following a snapshot is that you end up following something that is known to be wrong. That's obviously not the way to get interoperability! This has in fact been a real problem at the W3C, where mistakes are found and fixed in the editors' drafts of specifications, but implementers who aren't fully engaged in the process go and implement obsolete snapshots instead, including those bugs. This has resulted in serious differences between browsers. [1] https://whatwg.org/working-mode#additions https://whatwg.org/working-mode#additions
- kuschku 9y agoWHATWG standards don’t even deserve that name. A standard is something like ISO EN DIN A4. It is defined in cooperation with every stakeholder involved, it is specced, it is tested, and a stable definition is created. Everyone builds against this definition, and it works fine. The standard deprecates everything that existed before, and replaces it. That is a standard. It’s authoritative, basically immutable, and it is prescriptive. WHATWG "standards" come after the fact, only consider whatever browsers implement, refuse to ever deprecate anything (unless browsers have already deprecated it), and almost always just are "whatever Google Chrome does". That’s a disgusting abuse of the word standard. WHATWG "standards" are the equivalent of Microsoft Office Open XML, a standards body just taking an existing implementation, defining whatever it does as standard, and doing it so incomplete that the result is useless. Yes, WHATWG and W3C are doing the best they can do in the current climate (where Google can roll out QUIC and SPDY before even any standard is defined across websites accounting for 6% of global traffic, 65%+ of web browsers, and 85%+ of mobile phones), but this is just misleading. It helps no one to pretend to do standardization work when you don’t actually have any power to decide anything – neither WHATWG nor W3C can actually force, or even ask, Google to change SPDY or QUIC. They’re papertigers.