They need to learn a lesson about wantonly pushing proprietary technology when perfectly fine standardized solutions already exist. I suspect they haven't learned anything though.

I was going to write something about hoping those developers choke on a bucket of something but decided better of it. ;-) I'm a little pissed after years of fighting with web sites that require Internet Explorer because the developers were retards and used some proprietary MSIE shit.

>They need to learn a lesson about wantonly pushing proprietary technology when perfectly fine standardized solutions already exist. I suspect they haven't learned anything though.

I think they did learn. Keep in mind that back in IE4/5 era when most of that stuff was created, they were competing against Netscape 4.

If they did learn anything, it has been a slow process. The <canvas> tag for example, was introduced in Safari 1.3 and has been supported in Firefox since 1.5, Opera since version 9, and in all versions of Chrome. Contrast that with IE. The <canvas> tag is not supported by IE until version 9. If you want to do any cool <canvas> graphics in versions before 9, you'll have to use something like ExplorerCanvas at http://code.google.com/p/explorercanvas/, which of course mean more conditional IE comments in you HTML, and more pain for web developers.

That is because they didn't catch up that far until version 9.

The problem is enterprises, not consumers.

Exactly! Man the stories I could tell....

Even non-tech savy consumers get's their browsers updated once they buy a new machine.

But enterprise on the other hand. Boy is that a different story. They will on purpose maintain IE6 for as long as they can because they simply cannot even begin to deal with the support issues when switching.

If you want to make a lot of money on a one off. Develop a method for large enterprise to switch without the headache.