2 ms·
As long as Microsoft will not implement the same features, in a similar time frame and in a compatible way as the other browser vendors they should be blamed an
by josteink 14y ago
As long as Microsoft will not implement the same features, in a similar time frame and in a compatible way as the other browser vendors they should be blamed and shamed.
First Microsoft thinks HTML is too limited and creates new APIs which gets turned into drafts, which in turn gets standardized, albeit slightly differently from how Microsoft did it in the first place.
They get to choose to break all sites written for this API while still in draft, or get to break the standard. Whatever they do, people curse them for it.
Microsoft then says "You know. We get it. That sucked. We created that situation. It was our fault. Next time around, we wont mess around with draft-specifications in a release browser, luring people into prematurely using non-final specifications in production web-sites".
And now everyone hates Microsoft for being slow.
Evidently, as long as your name is "Microsoft", everything you do will be wrong, either it is a) pushing the limits, b) implementing the drafts, c) being compatible with deployed code, d) being compatible with the negotiated specification or e) waiting for the specification to be finalized.
Can someone please point me to the option f) which makes everyone happy?
If we held Google, Mozilla etc to these same super-hypocritical standards, I'm pretty sure everyone would just stop making web-browsers, since all you got for it was hell from ungrateful bastards.