News for hackers. Stuff that matters.
Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by baybal2 on Friday April 13, 2018 @05:07PM (#16833919)
> 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.

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by manigandham on Friday April 13, 2018 @09:44PM (#16835335)
Ok, 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?

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by baybal2 on Saturday April 14, 2018 @09:14AM (#16837192)
How it should work:

A standard is written and set in stone at least for 1-1.5 years. Official test suites are made.

Then, browsermakers make their stuff compliant.

APIs must support strict versioning. A user should not be bothered with "your browsers supports version 1 of method b, version 2 of method c, and does not support method d" it should either work with API version N or popup a big error message "API version N not supported, update your browser"

Re:Microsoft, Google, Mozilla, and Apple Object to W3C Fork ... by manigandham on Saturday April 14, 2018 @06:48PM (#16840007)
For the 3rd time, do you have an actual example of what's wrong?

In the 1.5 years of wait time you mention, the current process will have standardized and released features across all browsers. The web has changed and nobody wants to wait years discussing something. Compatibility is not a major issue because features are rapidly updated and there are compatibility tables that will automatically reference and even build your app for you with the proper polyfills and transpilations.

Sure, sometimes there are bugs and partial features, but this is rare and there's no evidence that W3C prevented this since implementations are not up to them.

However the W3C has definitely failed to make any progress with HTML/XHTML. They failed with SVG. They failed with DRM by completely ignoring the issues raised and causing the EFF to leave. So please state exactly what the W3C has done better and where they have added value because as far as I can tell, they are just wasting time every few months from the very people who are trying to move the web forward.