MozillaZine

Lockergnome: Why You Should Dump Internet Explorer

Wednesday June 16th, 2004

Chris Pirillo wrote in to tell us about a new article on Lockergnome entitled Why You Should Dump Internet Explorer: "The time has come to dump Internet Explorer. I know, I know — you may have heard the same thing before from those that think it's cool to hate Microsoft; but I'm not one of those guys. I'm actually an MCSE and I happen to like quite a few of Microsoft's products. Rather than lump me into the Microsoft-basher category, consider for a moment why you use the browser you use, and humor me by entertaining the notion — if even for a second — that switching to another might be worth your while..."


#14 Re: Re: Re: Re: You'll always need IE.

by pcx99

Thursday June 17th, 2004 7:19 AM

You are replying to this message

No, I know it's not an easy thing to do but the point is that the Mozilla/Firefox team isn't even *TRYING*. File a bug that says there are no tooltips with alt tags on images and you get smacked down (even insultingly so) because ALT tooltips aren't part of the w3 standard. In reality however there is already a feature in firefox to do this because there is an IMG tag which does have w3 sanctioned popup tooltips so exactly how many millions of dollars would it cost to tie the ALT tag into that same tooltip function? Probably about an hour to implement it on all versions and then do some minor tests and the return on investment would be a hundred fold.

The biggest obsticle to incorporation into corporate internets with web applications is that IE javascript allows you to reference an object by objectname.action while mozilla forces you to use document.getElementById("objectname").action (or assign a variable). Granted IE's version is a horrible corruption of javascript but because it was quick and easy and obvious, lots of back office apps use that and mozilla breaks those apps. But hey, how difficult would it be to catch the error by referring to the objectname directly and do a behind the scenes getElementById just to see if that corrects the error? Really not that difficult and it would make mozilla incredibly palatable for corporate intranets and back office developments.

In short, guarantee backward compatability with existing applications and web pages is worth the time and effort because developers will embrace what lets them get by without having to go back and revise all their old apps. If mozilla works with their existing web apps and then offers nifty tools and gizmos they can use to develop the ui of their next web app, well then mozilla my be a manadatory install. But if you're the IT guy and see mozilla doesn't work with the old apps (even if it doesn't because you were a sloppy programmer) what are the chances mozilla will be deployed next year instead of IE -- right, zero.

Until the outright hostility to anything not w3 is overcome in the mozilla decision making process I honestly do not see the browser being anything more than a niche oddity in the near future which is unfortunate because there is so much potential there.

If you have any doubts about how MS won the browser war just remember to check your server logs -- to this day IE still reports Mozilla/4.0 (compatible; MSIE 6.0 ) why Mozilla doesn't "get it" I have no idea.