Linked by Kroc Camen on Thu 25th Feb 2010 10:18 UTC
Humor BBC News reports "Mark your diaries for 4 March because in Denver the funeral arrangements are well underway for the planned passing that day of Internet Explorer 6". There's a phobia of being buried alive but I think in this case, it's the living that are all too quick to be shoveling the dirt over as IE6 doesn't officially die until 2014 when Microsoft pull the life-support.
Permalink for comment 411250
To read all comments associated with this story, please click here.
RE[4]: I like IE6, really
by deathshadow on Fri 26th Feb 2010 21:03 UTC in reply to "RE[3]: I like IE6, really"
Member since:

Im talking about supporting svg, text shadows, rounded borders, all new css3 stuff which i CANNOT use.

... most of which shouldn't be using on production code given the CSS3 specification is not even out of DRAFT. That's what DRAFT MEANS!!!

Lemme weave you a tale of a browser called IE 5.x; IE 5 in all it's iterations were the most standards compliant browsers of their time because by the time of IE 5.5 they had implemented as 'usable' most of CSS2 and all of HTML 4 - when both specifications were still in DRAFT.

When the specification came out of draft things like the broken box model, improper float behaviors and a whole host of other things became apparent - but fixing it would have broken three years+ worth of people coding to the broken model based on the draft specification... This is why IE6 added the doctype 'standards mode' trigger in the first place. Even with that trigger there are still errors and problems we code around...


Draft means not for production code - end of story. GET USED TO IT. It's like the retards who bitch about beta's being buggy. SAME THING.

It's also what -moz and -webkit means; If it was ready for real use on websites, it would be called by it's real name and not prefixed.

Draft is for playing around with to see what might be possible someday, and for testing to make suggestions before it goes final - NOT for making production code!!!

Besides apart from SVG and text-shadow (which in most cases the latter just makes **** harder to read) there isn't a damned thing you mentioned that cannot be done in HTML4/CSS2 via techniques like sliding doors - hell, MOST of the time you'll still want sliding doors instead of the auto-rounding of corners if you want gradients, control over the aliasing, or anything fancier than 'ooh look, I cut one corner off'.

Though it's funny you mention SVG since IE had SVG support BEFORE any other browser thanks to an Adobe plugin - **** like that is what plugins are FOR!

It's just Adobe dropped it like a hot potato when nobody gave a flying fig about SVG for six years so they bought out the owner of it's competitor - Macromedia. Moment they owned Flash... SVG became a discontinued second class citizen.

ONLY reason we got a new version in Jan '09 was because of a security hole. Even the 2005 release was a bugfix and it hasn't seen a real update since 2001.

IE is able to support SVG, you just need to write a activeX plugin to handle it.

Edited 2010-02-26 21:07 UTC

Reply Parent Score: 2