3 ms·
The most important versions of the HTML standard have merely codified the state of browsers at the time. The other W3C standards remain partially (or incorrect
by wvenable 17y ago
The most important versions of the HTML standard have merely codified the state of browsers at the time. The other W3C standards remain partially (or incorrectly) unimplemented so they're effectively not standards anyway.
The innovation on the web has always begun with the code -- and always with proprietary solutions. The best of these solutions are eventually implemented by everyone and that becomes the standard. Netscape added images, tables, and plugins. IE added events on all DOM elements, xmlHttpRequest, and so on. Different browsers are now beginning to implement "HTML5" features. When all the browsers reach some level of common usefulness then W3C or WHATWG will fit their standard around what's in common usage and call it HTML5.
Having big committees make big plans has never worked for the web.
- m0th87 17y agoHTML5 is a debatable chicken-and-egg; one could argue that the standard came first even though a few parts were implemented by browsers prior. And what about XML? SVG? Most of the examples you give are early innovations made by browsers because the standards committees were weak back then. I kind of feel like you need both (standard + code) for an effective solution on the web. One inevitably has to come before the other, but I don't think it's always code.
- gleb 17y agoAgreed. I like how JWZ put it: http://jwz.livejournal.com/147024.html?thread=760144#t760144 http://jwz.livejournal.com/147024.html?thread=760144#t760144 What's a "de facto standard?" It's what we call a standard. What's a de jure standard?" It's what we call a wish.
- jeff18 17y agoThat's not quite how it works. It's more like implementors (who make up most of the working group) create features, prefixed in a clear namespace e.g. -o, -webkit, -moz, etc. and then submit proposals for these features which are reviewed and reviewed, become standardized, and everyone implements the agreed upon solution. It is absolutely critical that these features go through this open process and are well documented. What you are describing is more akin to the Netscape - IE browser wars, which was terrible.
- rictic 17y ago"The innovation on the web has always begun with the code -- and always with proprietary solutions." Minor correction: lots of innovation has taken place in open source implementations first, which aren't proprietary.
- pbhjpbhj 17y agoYeah, knock up a few skyscrapers and then get an architect to draw some plans. What could possibly go wrong. Seriously I thought we were trying to do it right this time so that the 'net could move on and browsers could differentiate on features not on whether they bother to implement the standards properly.