4 ms·
I suppose the other issue was that IE was only available on Windows (although briefly on Macs too) and wasn't standard compliant.
by jonny_eh 4y ago
I suppose the other issue was that IE was only available on Windows (although briefly on Macs too) and wasn't standard compliant.
- HWR_14 4y agoIE on Mac was the most standards compliant browser of the time, on Windows or Mac. In fact, it's biggest flaw is that running on IE on Windows and running on IE on Mac required a lot of "different browser" code.
- mananaysiempre 4y agoOnly on Windows, well duh. Microsoft post-1990 stopped cross development as soon as they could, even though it’s not like they weren’t capable of it (Visual C++ 4 Cross Development Environment for Macintosh, OLE 2.0 SDK for same, COMsource and DCOM for Unix). I’ll never like it, but I can’t really blame their cold, dead moneymaking hearts for it, only myself if I ever expect anything else. I seem to remember it was due to some pretty old and involved behind-the-scenes agreements that IE for Mac even made it to 5.5, but once again finding the relevant scan on the DoJ website is beyond me. As for standards compliance, my recollections are principally of IE6 (last pre-arse-parking version) circa 2010, when it was indeed woefully behind the times. I expect that is what you are thinking of as well. But that is not the relevant characterization, is it? That would be IE6 circa 2002, and I read that at the time it broke Netscape-targeted sites because it did CSS 2 (etc.) better than Netscape, not worse. I didn’t even have an Internet connection at the time so I can’t tell firsthand (without scraping up an old Netscape or Firefox beta installer), but I can believe that.