Hacker News new | ask | show | jobs
by pilif 5744 days ago
Unfortunately, I have to deal with a much different picture in my case. The web application is often used by either complete computer illiterates or users in large corporate installations (or both).

My IE numbers (looking at the three biggest installations):

IE percentage: 80, 90, 98 - IE6 percentage: 30, 50, 40

No Chrome. No Safari. Rest is Firefox (2.0, 3.0, 3.5 and 3.6).

I weep when I consider the amount of development time we waste catering for these IE users refusing to (or unable to) update.

2 comments

I nearly fell off my chair when one of our new enterprise customers asked me if we could provide them the app... but with Firefox support because that was all they used.

Heaven :)

I worked for this large company, who had just bought another smaller company. Wisely, the smaller companies IT department had moved everyone onto Firefox, but since they had to have access to our new system, which was IE, we had to tell them to move back to painsville.

It broke our hearts, the IT people, and the users. The new system will work on all browsers (except IE6), whenever that will be out.

Out of curiosity, did you look into using something like IETab? You can configure it to render specific sites in IE's Trident engine, and all other sites using the usual Gecko engine.

However, I'm not certain how easy it is to push a Firefox extension + configuration to a large number of Windows machines.

You are very luck.
You are very grammar.
Chrome is a disallowed program on our network by "Symantec Endpoint Protection". You can install Firefox but it's discouraged by the IT department. I wouldn't doubt if these setups are common among larger corporations.
That's what it's like here. Fortunately, you can just rename chrome.exe to not-chrome.exe, then everything works fine. The "protection" software works just well enough to get the contract, but not so well that you can't work around it.
If that's this issue:

http://code.google.com/p/chromium/issues/detail?id=38

Then it appears to be resolved for some time now.

Another workaround here:

http://www.vaidy-dyngp.com/2009/02/google-chrome-symantec-en...

I suppose the issue was more that there are barriers which require the effort beyond that which the 98th percentile will exert for the benefit that Chrome gives, and therefore 98% of users will stick with what's given to them.