Internet Explorer Funny Nicknames

Microshaft Explorer

Mozilla? Phoenix? These are other names some people give to an excellent browser.

Good point paxx,

Is IE really the most popular browser, or just the most used one?

I guess you could look at it this way, because of the sheer number of people using IE, it is also the most loathed browser

'I Explode'....that's the browser, 'exploder.exe'...that's the shell/file manager...

Infernal Explorer...

Doesn't most popular and most used mean the same thing?

It did for the 'most popular girl' in my high school, HailStorm.

exploder.exe is a funny nickname for someone that promotes guncontrol
Boom! Boomer!! Meepmeep

I just call it Bill's anal probe...

about gun control....NOT...

I promise I will never divert a thread to that subject!!!!

If do, both Jafo and Paxx have permission to shoot me!!

I just feel happy and am in a good mood
I liked exploder, but now that I am having XP it is more a small poof sometimes

HailStorm, depends on the definition of "popular". If it means that it's what is the most used, then yes. But one could interpret "popular" as "the most liked". And because one uses something doesn't mean he likes it.
I don't really like Explorer, but I use it because a lot of lousy programers don't know how to program a web page so it's compatible with all browsers.

BTW. Note to all web programmers: if you have to do a detect browser script on your page, please don't detect the browser name. That's lazy code. Instead make your javascript detection based on whether a browser understand the code you are trying to pass. For example, Phoenix is rejected on some web pages, not because it can't understand the code (which it can), but because - understandably - nobody thought of adding "Phoenix" to the browser detection script. As I result, I get sometimes "This site can only be viewed by Netscape 4.7 or IE 4 or above."
Yeah right.

Paxx....Last time I checked IE had a huge (anywhere from 75% to 93% - depending on the study) percentage of the total worldwide browser market. Many employers cannot not justify the cost of adding (in most cases) hundreds of lines of code to support cross browser compatibility (expecially with the plethora of browsers/versions) in their intranet development. As I spend most of my time developing 'intranet' applications (where microsoft is the standard), I have to agree with them. Of course, this does not hold true for 'internet' sites (where cross browser compatibility is a MUST).

Pheonix and the other late-commers are so inconsequential (granted that many of them are based on the same engine) in the corporate marketplace that coding for them is pointless in most cases. Furthermore, most of the code you refer to (based on the NS 4.7 quote - where NS was not even near W3 compliance) was written long ago. I do agree with you that developers should attempt to handle as many browsers as possible, but it is increasingly difficult to wade through the crap people keep putting out there.

Peff...I may be pro-gun-control, but I'm also a 'crack shot' [Rifle range].
Lecrayon, I'm pro-coyote and anti-roadrunner....so 'meepmeep' to you, too...

Bill's ad: "Buy Exploder from ACME"
All I use is explorer..it does the job...

Peff, you didn't understand.
I'm not saying to support Phoenix. Phoenix is good enough to support most well coded sites. The problem is witht the browser detection script. Also Phoenix would understand the code on the site, the script rejects it because it's not called "Explorer" or "Netscape". What I'm saying is that a smarter way to code the script would be to program a bit of code and see if the browser understands it (no matter what it's called).
It's as if a bar had a list of everybody who is currently over 18 and checks people's names at the door instead of checking their age. Obviously, over time, new people turn 18 but are rejected at the door because their name isn't on the list.

paxx, so what you're saying is have a script that checks the DOM.

Yes.
For example, you need to use the roll-over event in a script, but you're not sure all browsers support it. Instead of doing a detect browser script, make your script so that browsers that don't support the roll-over event are sent a specific message or sent to another page.