3 ms·
In the history of the web, most of the standards have simply codified what was already in common usage. We've already seen problems with implementing large sta
by wvenable 16y ago
In the history of the web, most of the standards have simply codified what was already in common usage. We've already seen problems with implementing large standards after the fact: We had the box model problem in IE with CSS, for example. Some of biggest failures, like XHTML, were from standards committees and some of the biggest successes, like xmlHttpRequest (Ajax), just started out as proprietary features.
In my opinion, the best way for the standards to emerge is early and often implementation. It's best for everyone to be able to actually work with a reference implementation. This already happened, for example, with CSS gradients. It was a feature proposed by the WebKit team and Firefox took the idea and implemented it differently. Web developers got a chance to use both and weigh in on the pros and cons. Browser makers got to see how works in real situations. And, in the end, WebKit changed their implementation because the Firefox method turned out to be better and simpler. And now that has been put in the standard to become part of HTML5.
Microsoft isn't even in the conversation.
- kenjackson 16y agomost of the standards have simply codified what was already in common usage. But there's a BIG difference between saying, "OK, pretty much all of the top 5 browser manufacturers have implemented feature XYZ, and it is commonly used today by many popular sites in a standard way. Lets codify this." vs "WebKit just added this cool new feature. Opera implemented it two weeks after it shows up in WebKit. No one is really using it yet, but it's really cool. Write up a draft of it and now lets say its part of the standard (in-progress)". That's not codifying common usage. That is some vendors in key positions in the standards body taking advantange of their positions.
- wvenable 16y agoI agree. It's dishonest to say that Microsoft isn't implementing HTML5. But they've actually said something much more subjective: that IE is not a "modern browser". The argument, which hasn't really been explicitly stated, is that a modern browser attempts to implement these new draft features before they're standardized. In the past, Microsoft was not shy about implementing all kinds of new HTML technology but since IE6 they've only been doing the minimum necessary. You can't get around to codifying a commonly used feature if it never becomes commonly used. And it's pretty clear that all these new HTML5 features will be in common use everywhere else long before the HTML5 standard is finished. So even though Microsoft is going to be releasing a new browser shortly, it'll be obsolete almost immediately.