5 ms·
Because you already mentioned the difference: HTML is all about a standard for everyone. Implementing new features on your own is not much different from what
by buster 17y ago
Because you already mentioned the difference:
HTML is all about a standard for everyone.
Implementing new features on your own is not much different from what Adobe does.
For example: Let's say Firefox implements an API for Webcams. Will MS implement the exact same API in IE? Unlikely. First of all, the have Silverlight (i am supposing that Silverlight can access the Webcam as well, but don't know for sure). MS wants to push Silverlight and defend IE marketshare. With MS blocking this feature, it essentially means that noone will use it because every website is developed with the first requirement "Has to reach the vast majority of users", which in the end means "IE support".
They would eventually develop an own API, which turns out to be incompatible to Firefox' API if pressure is high enough.
Now, if you have the thought "but if MS/Apple/Google/Mozilla/Opera would agree on that new API", that's what the standardization process is all about.
- derefr 17y agoI did actually mean "the standardization process", I was just differentiating from the part of HTML5 that's about, well, HTML. This is more of a feature that belongs in the DOM exposed to ECMAScript, which the HTML5 movement seems to be all about pushing forward the standards for as well.
- wheels 17y agoWhat you describe is exactly the opposite of how HTML evolved up to this point. Usually precisely what has happened has been that browsers implemented things that the others didn't support, got some traction, were widely copied, and then, finally, standardized.