Linked by Thom Holwerda on Fri 22nd Oct 2010 22:11 UTC, submitted by google_ninja
Internet Explorer "There, I said it. Microsoft has been bombarding the media with claims about how much better IE9 is than all the other browsers, more HTML5 and CSS3 compliant than any other browser that ever existing and ever will. It's the only browser that passes all the tests they made up. And, Microsoft has finally implemented the CSS3 selectors that were implemented by other browsers back in, what? 2003? Because Microsoft has updated IE to support CSS3 selectors and rounded corners, they want us to believe that somehow IE9 magically supports the whole slew of CSS3 visual styling. I'm afraid it doesn't. As a matter of fact, IE9's support for CSS3 visual styling is so poor that the results are shocking."
Permalink for comment 446753
To read all comments associated with this story, please click here.
RE: End of days
by deathshadow on Sat 23rd Oct 2010 14:18 UTC in reply to "End of days"
deathshadow
Member since:
2005-07-12

Feels strange, does it not?

It's very easy nowadays to sit around bashing IE, especially IE6. Take that "IE 6 funeral" nonsense of just a few months back... Fact is, it's aged like milk and M$ disbanding the IE team and resting on it's laurels for half a decade put them squarely in last place...

Unless you count Amaya (and who the *** uses Amaya?) every release of IE from 4.0 to 6.0 were at the time of their release the most standards compliant browsers of their time -- Think on that! Lemme just say that again...

Every release of IE from 4.0 to 6.0 were at the time of their release the most standards compliant browsers of their time -- MIND BLOWING. It's easy to forget today just how far ahead of the curve IE 5.5 and 6 actually were... that's what killed off the competition in the first place and why with little or no extra effort I can usually make pages that work just fine all the way back to 5.5 with most every whizbang feature CSS 2.1 can deliver using a few simple bugfixes like inline-float, haslayout or expressions to recreate missing functionality like min/max-width/height.

When IE 5.5 and 6 were getting CSS 2 and 2.1 draft into something resembling working, Netscape was effectively running in place, gecko was a buggy unstable train wreck not useful for anything, firefox wasn't even a twinkle in a FLOSS fanboy's eye, Opera 4's alleged CSS 1 and 2 support had gaping holes in it that made IE 5.0 look complete... and that's before we talk all the stuff IE innovated.

Think back... First browser to even attempt to include parts of CSS2 Draft? IE 5.0. Ajax? IE 5.5! Properties that have been adopted into CSS3 like word-break? IE 5. @font-face? IE 5.5 with EOT support... Extensions? What do you think ActiveX controls are?!?

The really sad part is MOST of the problems with IE7 and lower are related to backwards compatibility BECAUSE IE implemented CSS2 DRAFT and people started deploying it on websites before it hit recommendations. Box model difference? Came after IE5 started implementing CSS width and height controls... We already had websites out there using it and forcing them to the new box model would have broken millions of sites; So they added the doctype trip since doctypes weren't part of the draft specification when IE 5 and 5.5 implemented the box model!

So what are we doing today? Developers everywhere starting to slap CSS3 up on their pages; a specification NOT EVEN OUT OF DRAFT YET... More things change, the more they stay the same. Right now the people making HTML5/CSS3 sites for real-world deployment are just setting us up for the exact same train wreck that the switch from IE5.x to IE6 was.

If anything, FF, Opera and Safari are to CSS3 as IE was to CSS2... and that's not necessarily a good thing for the future when/if we ever end up with a recommendation.

But as always, nobody seems to understand what words like "beta" or "draft" mean.

Reply Parent Score: 3