3 ms·
I don't think that's really true. Microsoft only tends to push incompatibilities AFTER it achieves dominance. For example, Internet Explorer was by far more st
by btilly 16y ago
I don't think that's really true. Microsoft only tends to push incompatibilities AFTER it achieves dominance. For example, Internet Explorer was by far more standards compliant than Netscape (at least through version 5).
That's not how I remember it.
Microsoft pushed lots of incompatibilities that had no uptake. (VBScript anyone?) Microsoft added lots of extensions to the standard. Because Microsoft did a good job on them, many made it into the standard and so now look standards compliant. (XML-RPC anyone?) But from the point of view of cross-browser compatibility, they were bad news at the time.
- TomOfTTB 16y agoI think you're remembering things from a Netscape perspective. For example you cite vbscript which was introduced a mere 8 months after Javascript (which was called livescript at the time to match Netscape Livewire). So they were competing technologies and not either side ignoring a standard (MS to their credit quickly rushed jscript out when Javascript started to become dominant) (Edit: I was curious so I looked it up. Javascript was implemented by Netscape in Dec. '95. MS implemented Jscript in Aug 1996. Javascript was adopted as the ECMAScript standard in June '97) As for extensions I don't think you can consider those incompatibilities. Both sides were doing it. Yet on the Netscape side they were actually taking parts of the standard and not implementing them (which is something the open source team had to straighten out after it was turned over: http://oreilly.com/news/flanagan_1100.html http://oreilly.com/news/flanagan_1100.html) You can even find old IE reviews that point out Microsoft was implementing standards far quicker (like this one I found via wikipedia: http://www.pcpro.co.uk/reviews/peripherals/671/internet-explorer-4 http://www.pcpro.co.uk/reviews/peripherals/671/internet-expl...)