Linked by Thom Holwerda on Wed 7th Oct 2009 17:36 UTC
Permalink for comment 388223
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
More News »
Sponsored Links



Member since:
2006-02-05
http://marketshare.hitslink.com/report.aspx?qprid=0
thats where i get my numbers from. They aren't perfect, but it is the best we can realistically hope to get.
there are a great many companies where you are only allowed to install software that has been vetted by IT. Firefox uses a non standard installer on windows, which makes it a royal pain to deploy on a windows network. That means that in big windows installations, unless you have a good IT team who are willing to go the extra mile, chances are you are stuck with IE.
The other issue is what you brought up, virtually any intranet webapp that was written more then about 8 or 9 years ago is probably IE only (and probably only IE6). This will make up the minds of even good IT teams to only vet IE, since that is the only browser that will work with their internal tools. Anything written the last 9 years or so has less and less excuse to be IE only, and nowadays if someone writes something that is IE only it is a pretty good sign of incompetence.
This is where IE still has a stranglehold, and if you are going to correct things through legislation, this is where you need to do it.