Udolpho.com |
|
Seven reasons IE is better than Firefox (from a developer's point of view)… Time to stir up the hornet's nest again:
1. In IE the contentEditable property may be applied to any element. This allows for sophisticated WYSIWYG and in-place editing within HTML pages. For mysterious reasons Firefox only allows this property to be defined for the entire page, which is a concession that satisfies no one.
2. IE's window.popup object allows the creation of custom menus and listboxes that exceed frame/window boundaries. This is a particular must for pages that use framesets (say, an editor with multiple control panes). There's no way to do anything like this in Firefox short of writing a plug-in.
3. window.showModalDialog and window.showModelessDialog offer vastly superior functionality to the very drab (and also non-standard) window.confirm or window.prompt. These methods are part of the icing on the cake that make IE so much more developer-friendly.1
4. IE's zone-based security model allows trusted sites to take advantage of features that might normally be prohibited, which allows developers the freedom to take advantage of certain browser features for special purpose sites (intranet, content management tools, etc.) without having to worry about what is allowed in the default lockdown mode. With Firefox it is all or nothing – it is impossible to permit features like Javascript for one domain but not another. The implications for the developer should be obvious. [This item previously referred to event granularity but the point only applied to older versions of the Gecko rendering engine, therefore I've updated it to keep the article relevant.]
5. IE is less resistant to making useful extensions to standards. This might sound like a reason to dislike IE, but standards compliance is much like
6. Firefox makes questionable interpretations of standards. For example, its childNodes collection assumes that a carriage return between block elements is a text node. There are very good reasons not to assume this, not least of all the longstanding practice of indenting HTML to enhance its readability. The result is a requirement for greater code complexity, and requiring more complex code (without providing any benefit) is never a good thing. Firefox does it a lot.
7. Lastly, Firefox has spurred the return of the browser button. Yes, you remember back when every other site had a little graphic reading "best viewed in Netscape Navigator" or "designed for Internet Explorer" or "made with a Mac"? This really dumb phenomenon – only surpassed by sites with lengthy Flash introductions that open themselves in new windows with the address bar hidden – was thankfully abated when Netscape's browser fell off the edge of the earth and Gecko development was still in its interminable beta years (Gecko being the rendering engine behind the meaningless Firefox name). But, alas, it has returned to annoy the world thanks to a new wave of determined morons. "Take back the web", "Burn down the web", "Stay in the basement" (I paraphrase), accompanied by a "cute" picture of a furry humping the planet,3 now clutter many pages like virtual bumper stickers. Please get a life, preferably offline, as this cult-like evangelism of a piece of computer software is beyond pathetic. By the way, people who use bumper stickers are obnoxious idiots.
Here then is the new browser button for Udolpho:
As you can see this utterly proves you must use IE instead of Firefox. Feel free to print this button image out and include it in your photo album of most precious memories.
Please send all hate mail via the Correspondence page.
Update: See Firefox Myths for a collection of myths regarding Firefox. Per most geek fascinations, a rather large number of bogus claims and assumptions exist about this browser. 1 Typically, Mozilla's Gecko engine attempts to reproduce some of the extra window functionality with proprietary extensions to the window.open method…NIH syndrome lives on. Needless to say no standards were involved during the coding of these extensions. So what if another browser already had a working solution?
The Gecko team of course screwed up the modal attribute in its half-assed extensions – apparently no one on the project really knows what "modal" means – but you can at least get modeless windows to work.
(NIH = Not Invented Here, a disease of the mind sadly prevalent among high-strung technical enthusiasts, causing them to completely reimplement incompatible versions of existing hardware or software made by "the other team". Hence extensions developed by the IE team are never to be used for any reason – you're a traitor or an imbecile if you do – but extensions developed by the Gecko team are self-evidently great and good – even if they don't work…you saw a lot of this sort of thing in old Soviet propaganda.)
2 From his essay "Self Reliance", a correspondent corrects me. I can't stand either of them.
3 What was intended as an exaggerated put-down is now reality.
Postscript: I just remembered an eighth reason: CSS expressions. IE has supported CSS expressions since 5.0. Expressions allow you to put javsascript in CSS properties, for example:
The downside to expressions is that if the page they are on is capturing a lot of events they can become performance hogs, because IE will recalc expressions every time Javascript runs. Depending on your class of computer, how many expressions are used in a document, and what events you are capturing (e.g. onmouseover), this can give the page a sluggish feel, especially when resizing. However, used with these caveats in mind it can be a very nice solution to a number of otherwise code-intensive tricks. Since it only works in IE it has also been used to come up with enhancements such as providing a max-width equivalent for that browser. |
| rss feed | atom feed |