6 ms·
Serious question: why are the W3C still publishing or trying to publish standards for DOM and HTML and probably a few others, when no one that matters cares abo
by chrismorgan 9y ago
Serious question: why are the W3C still publishing or trying to publish standards for DOM and HTML and probably a few others, when no one that matters cares about them? Why not rather throw in the towel on those particular standards and acknowledge that the WHATWG has won on them?
- Analemma_ 9y agoPolitics and pride, mostly. It's really rare and difficult for an organization to voluntarily admit that it has no purpose anymore and dissolve itself. That's what the W3C should do, but the realities of human psychology mean that's unlikely to happen.
- manigandham 9y agoIt's especially amazing that there's a comment asking what the WHATWG will give up in return if W3C gives this up... as if this is some kind of battle truce. These people are living in wonderland and need to wake up to the reality that there's already a winner and the war is long over.
- dragonwriter 9y ago> Serious question: why are the W3C still publishing or trying to publish standards for DOM and HTML and probably a few others, when no one that matters cares about them? There is a potential legitimate role for the two-track approach, if WHATWG represents a moving target of what browser vendors have agreed to implement and essentially is the vehicle for documenting hmthe agreed future common web platform, and W3C presents a versioned publication of the stable, widely implemented, currently usable state at a particular point of time; the W3C version would then be the target for conservative app developers that need something that works everywhere today, the WHATWG standard would be what people making browsers and other user agents would target, and what more ambitious developers willing to deal with “can I use...?” pitfalls would be guided by.
- manigandham 9y agoWhy cant people just use an older copy of the WHATWG standard as the new "stable" documentation? This is basically how caniuse.com and browserslist work today, allowing developers to precisely describe their compatibility targets and even automate their builds. It seems unnecessary to have an entirely separate organization to just copy/paste/publish new "versions" of existing archives.
- dragonwriter 9y ago> Why cant people just use an older copy of the WHATWG standard as the new "stable" documentation? Because the order of incorporation into the standard and the order of implementation and stabilization aren't the same, and some fesutres may be implemented incompletely in some browsers, so that what is stable and usable is a subset of features (and sometimes a subset of functionality within a particular feature) that doesn't correspond to any particular version of the LS. So you'd need manual curation. > It seems unnecessary to have an entirely separate organization Perhaps, though the audience and thus interested parties for the implementor-focussed spec and the developer-focussed spec are different.
- domenicd 9y agoThe WHATWG is actually the only organization I know of that publishers a developer-focused specification; see https://html.spec.whatwg.org/dev/ https://html.spec.whatwg.org/dev/. (We only do it for HTML currently.) Anyway, I agree with the grandparent poster that caniuse.com is a much better approach to documenting the interoperable subset than copying and pasting someone else's spec, and trying to delete the parts that are not interoperable by some threshold. We actually have caniuse.com boxes in the margin of the HTML Standard: see for example https://html.spec.whatwg.org/multipage/scripting.html#attr-script-type https://html.spec.whatwg.org/multipage/scripting.html#attr-s... Finally, it's worth noting that we only incorporate features into WHATWG Living Standards if they have multiple implementer interest; see https://whatwg.org/working-mode#additions https://whatwg.org/working-mode#additions
- BinaryIdiot 9y agoI don't really understand how this would make the two-track approach legit. Couldn't they just version the specification under WHATWG if that's what they're after? I just can't see a reason for the W3C to be handling any of this anymore except for money reasons.
- domenicd 9y agoIn fact, we already do publish commit snapshots for every change we make: https://dom.spec.whatwg.org/commit-snapshots/ https://dom.spec.whatwg.org/commit-snapshots/
- BinaryIdiot 9y agoThen what is the purpose of the W3C in this case? Many years ago I tried to get a membership to the W3C as I wanted to provide a voice for a company I worked for (and for myself, honestly) but found out that the lowest level of membership was many thousands of dollars. How can anyone who isn't already very well established ever be properly represented there? Then you check out WHATWG and, as far as I can tell, there are never fees associated with being a member and participating.
- domenicd 9y agoYeah, we try to make the WHATWG a welcoming place for all, with no pay-to-play structure. Please feel free to provide your voice there! We've gotten a lot of good community contributions and ideas.
- BinaryIdiot 9y agoThanks. I plan though :)
- currysausage 9y agoW3C process dictates that two implementations exist, not that all major browsers implement the whole standard. Thus, a W3C fork of the standard is of no practical use to “conservative app developers”. If you need to target specific (probably legacy) browsers, you check caniuse.com. By the way, the WHATWG HTML standard integrates little boxes with caniuse.com data. That is indeed useful to developers.
- c-smile 9y agoIt definitely needs to be some curation at least. As an example, CSS: Google came up with Flexbox, Microsoft came up with Grid. Now we have two competing layout methods doing pretty much the same. Yet they are conflicting in the sense that define the same flexibility entity by two different means: flexbox uses CSS property (that by itself conflicts with CSS 2.1 box model) and grid uses fr units for defining the same flexibility concept - portion of free space left in container from other fixed elements in it. Problem is that all browser from now on shall follow this mess.
- gsnedders 9y agoFlexbox and Grid coming from different companies isn't really relevant (and, to note, Flexbox comes from Mozilla originally, if I'm not mistaken, it is ultimately based on parts of XUL). They're also not competing: flexbox makes many 1D layouts easier than grid does. They're complementary, not conflicting.
- c-smile 9y agoYes, flexbox was an old Mozilla XUL's feature (<vbox>/<hbox>) where flexes were defined by attributes. We all agreed at the moment that having presentation attributes in markup is nto that good idea. And that CSS flex was no-brainer port of that thing by replacing DOM attributes by bunch of CSS properties. Problem is that flexbox ruins CSS box model that mandates that width CSS property is what defines the width of inner box of the element. Now they have flex-basis that if defined in galaxy far, far away overrides that width by something else. That above already recognized as a mistake: https://wiki.csswg.org/ideas/mistakes https://wiki.csswg.org/ideas/mistakes As of that 1D ... grid-auto-flow: row | column; makes flexbox obsolete at great extent.
- et-al 9y ago> Problem is that flexbox ruins CSS box model that mandates that width CSS property is what defines the width of inner box of the element. Now they have flex-basis that if defined in galaxy far, far away overrides that width by something else. I'm not quite following; may you please explain this? Thanks.
- forgot-my-pw 9y agoInteresting discussions from a year ago: https://www.reddit.com/r/javascript/comments/5swe9b/what_is_the_difference_between_the_w3c_and_the/ddl6xi8/ https://www.reddit.com/r/javascript/comments/5swe9b/what_is_... The W3C is very well funded and they don't wanna see the money gone.
- currysausage 9y agoIt really is all about not losing face. W3C/TBL had “owned” HTML and DOM for way too long to just acknowledge that they botched it and that their work on that has no practical relevance any more. “We are the organization that provides infrastructure for the standardization of stylesheets, and also some awesome-in-theory semantic web standards that are too complicated for actual implementations, and also some XML standards that are actually relevant for DTP” doesn’t seem to be the mission statement of choice for the creator of the web.