Slashdot Mirror
Problems at the W3C
dustin writes "Public outcry against the workings of the World Wide Web Consortium (W3C) is growing. On Sunday, Björn Höhrmann announced his departure in a lengthy critique of problems at the W3C. Web standards champion Zeldman adds his comments as well: 'Beholden to its corporate paymasters who alone can afford membership, the W3C seems increasingly detached from ordinary designers and developers.'"
That sounds great in theory, but what would probably happen in reality is that Microsoft would end up writing the standard, and adding proprietary, patented extensions onto it in order to ensure permanent dominance for Internet Explorer.
I would much rather have a somewhat supported open standard, rather than having a closed standard perfectly supported by one company.
We all know what to do, but we don't know how to get re-elected once we have done it
The summary mis-represents the bulk of Bjoern's critique, which less about the lack of non-corporate participation and more about the fact that the organization just doesn't work.
I wonder how the bulk of slashdotters, for whom a W3C standard seems to be a sacred cow, will react to the message that these standards are all-too-often ambiguous, bone-headed, poorly supported, slow-moving, and lacking important features.
That's not Microsoft's history with standards bodies. They come up with some ideas that rely heavily on their own technology. (Did you know that the first version of XSL used Visual Basic as a transform language?!) When the other participants fail to react with total enthusiasm, they decide that standards are overrated.
To be fair, Netscape in its heyday was just as bad as Microsoft when it came to ignoring standards. But I've long thought that both Microsoft and Netscape would have been more standards compliant if W3C had done something to encourage standards compliance. Like trying to issue standards on a timely basis, instead of just assuming that implementers would sit on their hands until standards were ready. Or like creating standards tests instead of waiting for third parties to do it.
But no, they just shrug their shoulders and keep creating standards that nobody will ever implement. W3C has not been effective for a very long time.
As long as clients ask for shiny spinning mouseover widgets and marquee scrollers on their crappy company homepages, and as long as us designers need their money, standards will continue to be meaningless. If Client X clicks on his little blue 'e' and sees what he wants to see, Designer Y gets to eat that week. I can suggest that their choices are bad, but the customer is always right (and I must quit bitching before he takes the project to his nephew who'll do it for free)...
Truly, I'd LOVE to be able to tell a guy, "No, sir, we can't do that. It's not supported by any of the current browsers." And then deliver a clean, stylish Zeldman wet dream.
The House Between - Original Sci-Fi Series
Well, just as an outside observer, it seems like the W3C is not very interested in "the web as application platform" -- instead pushing new document models like XHTML2 that don't really solve any realworld app dev problems.
At least from my POV, the stuff going on at WHATWG -- such as a vastly improved FORM model and standardized AJAX support -- will have much more relevance to the web in the manner that I and probably most other slashdotters build it.
Whenever I hear the word 'Innovation', I reach for my pistol.
You're exactly the kind of person I love to hate. "Oh, I can't use that, so I'll use this, which is just as bad if not worse."
First, Flash is as closed as closed can be. Second, it's completely proprietary. Third, Macrodobe only really support Mac and Windows for the Flash Player. Still no version 8 for Linux (and they themselves have announced that there never will be an 8 for Linux), while 9 is betaing for OSX and Windows.
I'd rather use the standards which have been "piecemealed together by a bunch of wacky nerds" rather than using something which limits people to using X with Y on Z running P which Q made you pay for because R told them to.
I may like some of the things done with Flash, but I really don't think it's well suited for doing full websites. Intros, sections of navigation, maybe. But it's too much of a resource hog, too bloated, and I hate not being able to navigate using the keyboard.
Goten Xiao
"A non-profit organization with a focus on development and maintenance of web standards" is exactly what W3C staff think the W3C is. What would prevent the staff of a new organisation from ending up in the same state?
The main problem here is that everyone who's in the "online biz" views the web as a tool to enhance their own leverage on their market share. MS tries to tie more parts of Windows into web apps so Windows has a leverage against alternative operating systems. Oracle tries to push their "web access enhancing" tools to gain market shares in the online database market. And I wouldn't be surprised if Apple was trying to get iTunes somehow into a webified form so they get a leverage on their online music share.
Nobody cares about the web or compatibility. Actually, everyone is trying its best to create as much incompatibility as possible.
W3C is standing in the way of big enterprises. Its very existance is a nuisance (not enough for a danger, but a nuisance) to the leveraging attempts of the big players.
So they have a really, really hard time. There's as far as I can judge nobody with big pockets on their side, but a lot of cash against them.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
I've been highly critical of Tim Berners-Lee leadership on the W3C. He established a structure that sidelined individual, mostly-disinterested members and replaced them by corporations interested in log-jam and difficult implementations that keep the small players away. The W3C was from the get go the antithesis of the IETF.
Tim then jumped into the dubious "semantic web" runaway train, full of inflated promises but bereft of actual results. The "semantic web" is high-risk research best left in the hands of academia. A standards body organization should be focusing on how to make the web better today, by improving on the current protocols, not on day dreaming about HAL-like computers.
Internet Explorer 7, which hasn't even been released yet, will not support large sections of the CSS 2 specification, published by the W3C in 1998. If you think the W3C are behind everybody else, then I believe you are only looking at the bits and pieces of their specifications that are actually implemented by the browser developers. With that twisted reasoning, it's logically impossible for them to be ahead.
Rounded corners are in CSS 3. Browsers haven't finished implementing CSS 2 yet. What's the point in the W3C racing even further ahead when the lack of browser support means it won't make any difference for years to come?
CSS 3 is a group of specifications, not a single specification, and some of them are ready to be implemented. So the answer to your question "How long?" is "Already there."
Bogtha Bogtha Bogtha
CSS is a tree decoration language. HTML is a document tree language. Why would they use the same syntax? That's like saying C++ should use the same syntax as XML. Or that PNG images should use the same syntax as e-mails. You use the right syntax for the job.