Ah! Well, well ….
And, this is precisely (though there are still many more reasons) why IE is still not dead!
Reasons are coming by own its own, isn’t it hilarious?
It's not that anybody's "faith is too strong to be shattered". Old IE still hangs on in the corporate environment because of custom ActiveX controls in internal applications. IE6 is a special problem, mostly because of inline CSS, but encapsulating the CSS and moving it into easily-modified external stylesheets is not that big a problem with a decent text tool.
#
So, there is the compulsion.
And so, after all IE6, the most popular IE version ever, is not so great.huh?
Getting ActiveX controls to work in non-IE browsers is a different class of problem altogether -- they purposely violate sandboxing for things like file system integration for line-of-business automation. There are some tools set for inclusion in HTML5 that may help, but the only real alternative right now, today, for ActiveX in the browser is Java, and if you're going to have to write applets, you might as well write apps.
#
And, that very IE’s ActiveX brought the concept of ‘computer security’ or rather ‘computer vulnerability’ into the real world too.
Without IE’ActiveX, ‘computer security’, ‘computer vulnerability’, ‘exploits’ and what not – would have been in PhD books/thesis only
or would have been an urban myth in some La La land.(I’m taking about mode of propagation only.)
Can’t be more be thankful for providing malwares a gateway to other’s computer.
I completely AGREE that Oracle (erstwhile Sun) Java is ‘definitely’ the better alternative.
(It is perhaps going to be one of those ‘once in a while rare celestial event’!)
Don't forget, ever, that Internet Explorer used to be thousands of miles ahead of anything else out there. IE4, IE5/5.5 and IE6, when new, allowed not only web sites, but web apps[/]. Almost everything we take for granted in modern web development came from Internet Explorer: Ajax, direct access of document elements and CSS weren't on anyone else's map at the time they were introduced in IE. (Netscape owned the web, and if you ever worked with layer addressing or JavaScript Style Sheets, you'll know exactly why Microsoft won the day.)
#
Never going to forget those horrific days, they haunt me like night mares!
Someone way-way back, first built an application with tabs, so should every application (including browsers) be thankful for that for an eternity?
More so, if someone from that fraternity comes and claims everything around tabbed application is due them.
And, the fraternity keeps reminding that everyone should be thankful and that too time and again?
That’s preposterous!
I don’t think such kind of Nepotism/Arrogance/etc would help anyone.
MS won the day because of the OS-cum-IE (plus Office) combo compulsion only.
Also, how they got them? I’m leaving that for a different discussion thread.
And, now you can see it happening in reverse-order.
Windows’ share has been declining and so is that of IE’s.
Do I need to talk about ‘at what rate’? I don’t think so.
And while we like to complain about the IE box model in CSS, that was something Microsoft got right -- CSS3 finally lets us force other browsers to use a width property that describes the width of the container without having to calculate through a nested hierarchy of border and padding widths for all of the container's descendants. Mozilla, though, took the programmatically easiest solution for the browser devs, and Netscape had the juice on the CSS working group, so we've had to deal with the borken (spelling intentional -- if you're going to talk about geeky things, you need to use geeky vocabulary) version since the spec was adopted.
#
C’mon! Stop the time-travel!
Couldn’t defend its past, so let’s be over futuristic - CSS3 is yet to be drafted.
That’s not a sounding reasoning.
Expecting a paradox in future every time - that’s childish.
Let’s talk about ‘present’!
And in the present, even though CSS was on their map very early when no one else had a clue, yet they still suck when it comes to implementing current CSS.
Now, given that internal corporate applications are the main reason why corporate desktops have browsers at all, compatibility with internal applications is the main concern for IT decisions.
#
That’s a too naïve logic to say the least!
Do you honestly believe that anybody is going to spend tens of thousands, or even millions, of dollars to convert away from working, stable, bug-fixed applications if they don't have to?
#
I cannot honestly believe that “somebody” is spending “tens of thousands, or even millions, of dollars” in the first place by using Windows and there by IE.
Big corporate who looked around for “options” are now saving 10 million pounds annually.
Moving on from the mumbo jumbo history class to yet another interesting class….
Therapy! Right?
Oh enchante!
If you do, there's therapy for that.
If you hadn't even considered that, well, welcome to Crossfire, a forum for actual argument. Thought, facts and logic are not optional.
#
I guess a large, really large room would be needed for that therapy session.
Make sure arrangements are made for the following ‘need-special-attention’:
Governments (US included), USDoD, USFAA, Google, IBM, London FTSE, NYSE, CERN and many other alleged clowns may (will) drop-in without prior appointment.
Now, either they don’t have those “internal corporate applications” or they are not suffering from a condition of “needless spending on a spree”.
Well, when it comes to therapy, I admit it I ain’t a master in it like someone else might be.
But, there is a classical symptom to check if something is ‘borken’ and doesn’t it go like this: First the denial then finally the acceptance.
Correct me if I’m incorrect that it is more than just a “logically true factual argument”!
“King Trident lost his crown due to complacency and ego that he can’t be defeated!”
Waiting for IE to go Dodo way!
First the denial then finally the acceptance!
I rest my case.
Peace Out!