Thomas said:
"wannabes" *doesn't* mean at all "loosers".
But if this is too upseting for your ears then "other browser producers
targeted to take leading positions on the browser market".
Nobody was forced to do anything. It seemed like a good idea and there
was no standard at the time, therefore it was implemented. And it was
implement without ActiveX.
Totally right. But it did not and it can not make the original
(IXMLHTTPRequest) non-standard. Same way if one paints a copy of
Jokonda, it doesn't make the original worthless
Presuming I'm developing a new browser (non-Gecko based) with
XMLHttpRequest support, what official paper should I follow to make it
standard-compliant?
http://www.w3.org/.... ???
http://www.ecma-international.org/....???
Nonsense. If Microsoft would push this to be a W3C standard, it is not
unlikely that it becomes one.
But it did not. Microsoft doesn't want to puch ActiveX by itself on
anyone. But they are targeted to puch Internet Explorer as hard as they
can - which is not a crime, averyone wants the same with their own
browser.
Why? Please be sure that I'm not a Microsoft defender.
But taking the situation as it is: side A invented a technology, side B
implemented this technology later on another basis. Neither of both
implementations are part of any international standards. One says "B is
the standard one no matter what". I'm still asking why?
And what you comfortably forgot to mention again is that Microsoft Corp.
is a full W3C member as well, as that allows you to distinguish between
Microsoft ("good guys") and W3C ("bad guys") in your own twisted way of
percepting reality.
In my presumably twisted reality there are no "good guys" and "bad
guys". Microsoft, Inc. is not an Empire of Evil and Mozilla Foundation
is not a Jeday Union. it's all for teens.
The only evil (as I'm not tired to repeat) is an absolute dominance of
one force on the market - and in this domain I do not care who could it
be: W3C, Mozilla or Microsoft. Any absolute dominance leads to
stagnation, and end-users are forced to eat the only one available
meal... or stay hungry.
Also there is a cardinal difference between ECMA International and W3C.
ECMA Internation is not appointed / self-appointed to keep and develope
ECMAScript. It is just a broad range standartization bureau. They can
write for you (based on provided specs and samples) ECMAScript,
microchips know-how or TV set user manual, just gimme money.
Therefore TC39-TG1 group members activity and communication to each
other is the crutial and the only force giving the trend to the further
ECMAScript development. Plus of course our (user and developers)
feedback and complains.
<
http://msdn.microsoft.com/library/en-us/dnclinic/html/scripting07142000.asp>
is dated July 14, 2000 but became actual again.