3 ms·
What a monumental waste of time. Why not just ignore W3C entirely? Seriously, what exactly are they going to do? Publish more? Sometimes it's better to not be
by manigandham 9y ago
What a monumental waste of time. Why not just ignore W3C entirely? Seriously, what exactly are they going to do? Publish more?
Sometimes it's better to not be nice and just let reality finish the job. So much effort taken from people who clearly have better things to do...
- BillinghamJ 9y agoYeah to be honest, at this point, it seems that the WHATWG members should just declare their withdrawal from W3C entirely, leaving it to die. It doesn't serve any purpose for the HTML standards any more.
- panic 9y agoThere's more to the web than HTML, though. Most new web standards are developed through W3C working groups.
- dmitriid 9y agoAnd those are often horribly mishandled. DRM was pushed through despite objections: https://www.eff.org/deeplinks/2017/07/amid-unprecedented-controversy-w3c-greenlights-drm-web https://www.eff.org/deeplinks/2017/07/amid-unprecedented-con... SVG was all but abandoned (the full story here: https://codepen.io/AmeliaBR/post/me-and-svg https://codepen.io/AmeliaBR/post/me-and-svg)
- kbrosnan 9y agoUnless you follow browser or specification development you are unlikely to know about WHATWG. In talking to teachers and web developers few know about the difference between the W3C and WHATWG. The W3C still has the mindshare lead.
- baybal2 9y agoW3C attempts to make proper web standards. Apple Google MS break them and and try to push for substandard specs pushed through W3C. As a web developer for 11 years, I can state that web development is devolving to chaos of IE6 era. When W3C allowed itself to be subverted and let big dotcom browsermakers to hijack the process. A result of that is the continuous bloating of the acting web standard, when you have dozens of new abandonware APIs being showed into the spec on a whim, and no focus on things that should really matter. It is 2018, and yet browser makers still have open CSS bugs from the previous decade that are banal to fix, yet all they care is how to stuff yet another API useless outside their own business setup.
- manigandham 9y agoThe only "standard" that matters is the one everyone uses. Everything else is a nice wish list for discussion but eventually needs to get out of the way. The WHATWG doc is a fine standard, backed up by real implementations. Beyond that, W3C is just copy/pasting whatever WHATWG has every few months so what's the point? And you really think the web is in chaos? We're at an incredible era of possibilities because browsers like Chrome constantly make progress instead of devolving into a bike-shedding argument for years. What APIs do you find so useless or abandoned and why can't you just not use them if so?
- baybal2 9y ago> The WHATWG doc is a fine standard, backed up by real implementation. It sucks badly. To begin with, it can't be called a proper standard. It is in their terminology "a living standard" which means it being changed on a whim. It is not being written as an "ideal prototype", but rather it is just a codification of current behaviour of how Google's devs managed to write Chrome's DOM Api, with with all bugs and workarounds. From standpoint of a person capable of high technical reasoning, this approach is bad. And... I can't believe that whatWG specs are being written by people hired by Google for 100k+ a year, they are not done on a level of what an any much professional technical writer should work on.
- manigandham 9y agoOk, so why does it suck? Because you don't like it? Why isn't it a proper standard when it's the only one implemented? Things definitely do not change on a whim and there's great care taken in the process. The group is very transparent and clearly state the objective is to keep the standard modern and evolving. You can always refer to an archived snapshot or the numerous compatibility tables for historic data if needed. Chrome has bugs, like any other implementation, but has moved the web forward greatly in the last decade and the vast majority of developers and end-users would rather have modern working tech than some idealistic document that doesn't go anywhere. Again, since W3C just copies the WHATWG standard anyway, what is the value that you claim is being added? And if you have better ideas, why not just contribute them to WHATWG instead?
- forgot-my-pw 9y agoW3C is just too slow and the web needs to move faster.
- sixdimensional 9y agoActually, they certainly can - both can co-exist peacefully and feed of each other. I think really this is all kind off a non-issue and stems from a lack of understanding about standards development. WHATWG is very much a definition of a "de facto standard" [1] vs the W3C which is more a "de jure standard" [2]. There is a conflict between the two, yes, but both can reasonably exist. [1] https://en.wikipedia.org/wiki/De_facto_standard https://en.wikipedia.org/wiki/De_facto_standard [2] https://en.wikipedia.org/wiki/De_jure https://en.wikipedia.org/wiki/De_jure
- manigandham 9y agoBut why do they both need to exist? I'm sure they can, since they have up till now, but what benefit is there? W3C is literally just copying the WHATWG documents so I don't see what value it's adding.
- hungryfoolish 9y agoIt's not just copying stuff, it's adding/editing to it. Criteria for such additions/editions seems to be browser interoperability, accessibility, internationalization etc.
- currysausage 9y agoYes, in theory. https://stackoverflow.com/questions/6825713/html5-w3c-vs-whatwg-which-gives-the-most-authoritative-spec/43082734#43082734 https://stackoverflow.com/questions/6825713/html5-w3c-vs-wha...
- dragonwriter 9y ago> What a monumental waste of time. Why not just ignore W3C entirely? Transition costs are probably a factor: as long as the W3C exists and there are web developers who might think it is authoritative, browser vendors will get flack for deviations between browser behavior and W3C specs. If they abandoned W3C that would eventually taper off as people would come to disregard W3C, but it would take time. It's in the browser vendors interest to keep W3C standards as meaningful as possible until W3C gives up entirely, but their involvement makes it less likely that it will be abandoned even if it is largely superfluous.