News for hackers. Stuff that matters.
Re:HTML 5 gets forked up by gioele on Monday July 23, 2012 @07:45AM (#4280483)
«All of which leaves just one question: what has the W3C ever done for us?»

It has given us good specs fixed in stone you could develop against and be sure that your code could still work in the next decade, thing XML or XSLT. Stable specs are also good for legislators and regulators, for they have the ability to pinpoint names and versions like "The minimum accessibility level for public websites is WCAG 2.0 level AA" instead of "all public websites must have a minimum level of accessibility".

We can debate whether the W3C model is good for a spec like HTML that is subject to so many business interests, but what standardisation model has been good for many other specs.

Re:HTML 5 gets forked up by Alex3917 on Monday July 23, 2012 @09:23AM (#4280798)
"It has given us good specs fixed in stone you could develop against and be sure that your code could still work in the next decade"

A lot of the W3C specs are actually so poorly specified that none of the browsers can even figure out how to implement them. E.g. in CSS the width of a pixel is defined relative to the length of each user's arm.

Re:HTML 5 gets forked up by stingraycharles on Monday July 23, 2012 @11:41AM (#4281488)
> CSS the width of a pixel is defined relative to the length of each user's arm.

I had to see this for myself to believe it.

"The reference pixel is the visual angle of one pixel on a device with a pixel density of 96dpi and a distance from the reader of an arm's length. For a nominal arm's length of 28 inches, the visual angle is therefore about 0.0213 degrees. For reading at arm's length, 1px thus corresponds to about 0.26 mm (1/96 inch)."

Source: http://www.w3.org/TR/css3-values/

Re:HTML 5 gets forked up by Alex3917 on Monday July 23, 2012 @11:49AM (#4281539)
Seriously, it's pretty messed up. Maybe IE6 didn't actually have a float drop error, it's just that my arms were too fucking long.
Re:HTML 5 gets forked up by jamesbritt on Monday July 23, 2012 @01:00PM (#4281922)
A lot of the W3C specs are actually so poorly specified that none of the browsers can even figure out how to implement them. E.g. in CSS the width of a pixel is defined relative to the length of each user's arm.

Once upon a time the W3C site pointed out that they did not define standards. They offered recommendations with the idea that people would implement them, see what worked (or didn't), and at some point a standards body (ISO, ECMA) would issue the actual standard.

However, so many people keep referring to W3C recommendations as standards (mostly as a way to brow-beat people into following one or another preferred practice) that the W3C changed their tune and decided to go along for the ride.

Instead of seeing W3C TRs as the last word we would be better served if people viewed them as (likely) incomplete works-in-progress on the way to ironing out well-defined standards.

Re:HTML 5 gets forked up by pak on Monday July 23, 2012 @03:39PM (#4282686)
relative to the length of each user's arm

It's easy to snidely dismiss that idea, but seriously, how would you define a unit of length in an environment that is supposed to translate between multiple devices and media types? A "pixel" makes little sense when drawing on a sheet of paper or a super-high DPI screen where pixels aren't individually visible. It can't be a fixed real-world distance, because pixels would sensibly be larger at movie-screen distance than at arms' length. They basically defined it in terms of the arc-length of the picture upon your eye, which is completely reasonable to me.

Re:HTML 5 gets forked up by lparry on Monday July 23, 2012 @07:59PM (#4283635)
I don't think they should use the word pixel to describe something that they're clearly defining as not an actual pixel.
Re:HTML 5 gets forked up by tzs on Monday July 23, 2012 @04:24PM (#4282912)
Actually, for something that is going to be fixed in stone, using units based on the length of the arm has a lot of historical precedent. See, for instance, the great buildings of ancient Egypt.
Re:HTML 5 gets forked up by grimboy on Monday July 23, 2012 @08:04AM (#4280527)
Yes, but apart from good specs fixed in stone, XML, XSLT and WCAG, what have the W3C ever done for us?

(It was a Monty Python reference.)

Re:HTML 5 gets forked up by bkardell on Monday July 23, 2012 @08:38AM (#4280605)
Specs are good, but they really aren't quite fixed in stone, things reach and then leave rec status. CSS 2.1 spent like 13 years going in and out of different statuses and only very recently appears to have been "completed".
Re:HTML 5 gets forked up by brudgers on Monday July 23, 2012 @08:56AM (#4280682)
But which shoe should developers follow?
Re:HTML 5 gets forked up by TylerE on Monday July 23, 2012 @09:01AM (#4280693)
Yes, W3C is good for having set-in-stone specs 5 years after they've ceased to be relevant.
Re:HTML 5 gets forked up by olalonde on Monday July 23, 2012 @07:08AM (#4280411)
The actual mailing list post is much more informative in my opinion: http://lists.w3.org/Archives/Public/public-whatwg-archive/20...

The "living standard" model is explained here: https://plus.google.com/107429617152575897589/posts/NZBJe6Jj...

Re:HTML 5 gets forked up by rjtavares on Monday July 23, 2012 @07:17AM (#4280427)
It lacks the great Monty Python references, though...
Re:HTML 5 gets forked up by untog on Monday July 23, 2012 @09:04AM (#4280714)
To be sure, this isn't a perfect result. Having specifications that can change is A Bad Thing. But having a standards body that is utterly unable to keep up with the times is arguably worse, as they end up being totally irrelevant. Look at HTML5- no-one is going to wait until 2014, when the standard is finally ratified. "The Standard" is what we're all using.
Re:HTML 5 gets forked up by Kilimanjaro on Monday July 23, 2012 @10:11AM (#4281021)
As long as chrome, safari, firefox and opera stick together, the web will move foreward.
Re:HTML 5 gets forked up by chimeracoder on Monday July 23, 2012 @12:57PM (#4281906)
Webkit is already a dominant rendering engine (36% plurality share) used on multiple platforms. Ignoring IE, which has historical problems of its own, Firefox is the only popular browser that doesn't rely on Webkit.

Take a look at this graph, and mentally add Chrome, Safari, and 'Mobile': http://en.wikipedia.org/wiki/File:Usage_share_of_web_browser...

While Webkit has advantages, and while I happily use Chrome for most purposes, I dislike the idea that a single implementation can become the de facto standard for proper rendering, perhaps even more so than the official spec.

1995 was almost twenty years ago. Not ten minutes ago, I tried to use a website which told me it required IE 6.0+ or Firefox. Do we really want to move to the days where websites will boast a 'Best viewed with Webkit' button?

Re:HTML 5 gets forked up by ricardobeat on Monday July 23, 2012 @02:24PM (#4282319)
Why would you ignore IE in this context? There are four engines in use, each with millions of users. WebKit is only way ahead in mobile, but it's only going to lose share from now on.
Re:HTML 5 gets forked up by sbuk on Monday July 23, 2012 @03:18PM (#4282595)
Gonna have to bite; why?
Re:HTML 5 gets forked up by daledavies on Monday July 23, 2012 @12:52PM (#4281889)
Interesting to see Google described as a "text ad giant".
Re:HTML 5 gets forked up by KaoruAoiShiho on Monday July 23, 2012 @10:18AM (#4281065)
This is more like a branch than a fork.