I know of many large sites that use IE 6 because the IT staff wrote IE-specific “web” applications that will now cost a fortune to re-write for some other browser.

IE 6 is a problem *created* by IT “professionals”, to see them ridiculing users (most of whom don’t give a rats what browser they use, as long as they have time to learn how to use a replacement and migrate their user settings, bookmarks, etc.) is pathetic.

Many of these same IT staff still say that truly cross-browser applications are impossible or too hard to write. They are incompetent idiots who hide behind crap like this and blame the browser rather than their own bad technology choices.

How about a little honesty rather than stupid ploys to re-direct the blame?

Bad inference. What does that have to do with filter support? Nothing, right?

Try to realize that any browser that has both a truthy document.call and falsy !window.XMLHttpRequest gets that code.

Inflicting the poor user with that (incompetent) approach is unfair. Not everyone can upgrade her browser, and maybe, just maybe, she’s using browser with a truthy document.all and a falsish window.XMLHttpRequest.

Getify gets it. Sad nobody else seems to remember similar WaSP F*Ups.

Anyone else tired of the garbage these guys blog about? comp.lang.javascript

@timdown: Sorry mate, but you’re the one who’s whining here, ironically. If people insist on using an outdated, unsupported and horribly insecure browser, then quite frankly, they can get what’s coming to them.

Web developers try to create awesome, standards-compliant and cross-platform websites that perform well on a variety of hardware, and scale across a variety of different media/screen-sizes.

IE6, with it’s s*itty standards compliance, numerous known yet unfixed bugs and overall general bugginess is an attempt to stymy all the innovation that’s going on in the web field. Even Microsoft has basically admitted that they were attempted to poison web standards with in, and they’ve basically fessed up and said that they’ll play nice with the other kids now, going forward.

This post was a bit tongue-in-cheek, but I think it reveals the sentiment of many web developers – we’re sick and tired of support ignorant sheeple, who refuse to use a real web-browser, like Chrome, Opera, Firefox, heck, even IE7/IE8/IE9.

Even Microsoft has basically washed it’s hands of IE6.

I don’t think you’re going to find much support here, sorry.

Cheers,
Victor

http://www.catswhocode.com/blog/6-html-and-javascript-codes-to-crash-ie6

Using code from that site the ‘effect’ you create is even more convincing.

If you really want to stop people from using IE then blurring a page wont help that much, the basic functionality (the ability to read) is still there and IE 6 users are probably able to put up with all kinds of quirky behavior. Crashing the browser is different. If an application crashes the non-geek user will invariably blame it on the application itself. If it crashes often they will stop using it.

Now we only have to really want to get rid of IE 6 enough… And by the way: Blurring is not devious, I mean really. This is.

I’m not saying that every detail has to be the same, but sabotage is pretty unprofessional.

The above comments are for people who don’t understand that this article is intended to be more humorous than a recommendation.

Sorry but this just isn’t true – sure there are retraining and deployment costs, but the killer is the cost associated with fixing/redesigning the multitude of internal web applications that only work with IE6. I don’t think there are many companies who maintain it as a standard by choice; I think it’s the massive overhead involved in moving away from it that discourages it.

“The majority of the population in third-world countries can’t upgrade IE6 because they’re using pirated versions of Windows (installed by the computer store). As you know you can’t upgrade to IE7/8 if your Windows is pirated.”

Untrue. Upgrading to IE8 works without problem even on not registered Windws copy. And anyway, there are still many other free browsers to choose, Firefox, Opera, Chrome, …

Maxthon is very popular in some countries, and as you know, those programs are shells over the computer’s default IE engine.

So what is productive about coding numerous workarounds and hacks to support such outdated technology? After 5 years in the front end game I’m over the code bloat and so is everyone else. I feel I could be a much more productive engineer if I didn’t have to support IE 6.

IE 6 MUST DIE. Viva La Revolucion