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.
Thread beginning with comment 411340
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: So...
by nt_jerkface on Sat 27th Feb 2010 09:18 UTC in reply to "So..."
Member since:

Yea that must be it. They must be slothful. It can't be that they don't like wasting their time with a legacy browser.

A web developer who works 40 hours a week can be far more productive if he doesn't have to target IE6. But according to you he must be lazy if he hates spending his time on IE6, even if he works 40 hours regardless.

I was working on an ASP AJAX web app last year and at some point it became apparent that getting the interface to look right in IE6 would take more tweaking than all the other browsers combined. It isn't just about CSS and PNG hacks. IE6 pukes all kinds of weird problems with AJAX.

Here's an example from the forums:
We have implemented an <asp:menu> control for site navigation, the menu has four main categories, and is at most 2 levels deep in some parts, there are in total around 40 menu items; we add/remove menu items dynamically depending on user permissions. Now the problem with IE6 is that if a user spends some time hovering over the menu items, the browser eventually crashes.

Sometimes a combination of valid JavaScript, Style Sheet, and DOM manipulation will crash IE6.

As for a fix, I'd recommend upgrading your web browser to IE7.

But you think not supporting IE6 makes you lazy? Maybe a website that doesn't support 200 languages has lazy developers as well. Or maybe they have limited resources and want to use them effectively, just like web developers who would like to make effective use of their time. IE6 wastes time by requiring extensive tweaking that is not required for other browsers. Some websites keep a separate IE6 site so they don’t have to bother with endless hacks. IE6 is not only the bane of web development productivity but a giant security risk as well. .

Reply Parent Score: 2

RE[2]: So...
by deathshadow on Sun 28th Feb 2010 02:35 in reply to "RE: So..."
deathshadow Member since:

Great example of what I meant by outdated, outmoded or just plain broken methodology used by people who can't take the time to understand what they are doing.

An ASP:menu instance, and you wonder why it breaks... Again, cutesy crap for what should be a simple non-scripted CSS menu for modern browsers with a .htc for IE6 - you don't even need to rewrite it anymore.

Unless of course you are using trident as your UI engine for a local crapplet - which is EXACTLY the type of crap that made many businesses unable to leave IE6 in the first place.

I'll admit - that's not lazy, that's outright ignorant. I'd have to see the actual page with problems, but I suspect the problem is the use of scripting and ASP bull for something that needs NEITHER.

Though it is amusing how obscure and ridiculous the 'problems' get as people try to defend their anti-IE6 viewpoint; since most always it's from trying to do something the hard way - and usually making MORE work for themselves in the name of making it 'easier'...


Edited 2010-02-28 02:37 UTC

Reply Parent Score: 2

RE[3]: So...
by nt_jerkface on Mon 1st Mar 2010 03:31 in reply to "RE[2]: So..."
nt_jerkface Member since:

So your response is....YouDon'tNeedThat(tm)

What about all the problems IE6 has had with updatepanel? What would you tell companies in that case? You don't need partial page updates? You don't need ASP AJAX?

Oh and I could list dozens of IE6 / ASP AJAX conflicts if you would like. All kinds of random crap that happens from pushing IE6 farther then it was ever intended to.

If you had spent a significant amount of dealing with IE6 issues you wouldn't be so defensive of supporting it. Yes some jobs require supporting it. That doesn't change the fact that it significantly reduces web development productivity and encourages legacy design as a way of avoiding conflicts.

You seem to be a very vocal supporter of wasted productivity. Perhaps a position with the government might suit you better than web development.

Reply Parent Score: 2