Linked by Thom Holwerda on Fri 12th Jun 2009 13:55 UTC
Permalink for comment 368225
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/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
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-07-24
I made no such claim. My claim is that you put too much credence into them. This point goes well beyond questions regarding the accuracy of the numbers. It extends to just what this sort of data is able to tell us at all. While business usage of public sites is no doubt covered... what do these statistics say about what happens after the employee logs into their warranty service provider account over at http://www.warrantycentral.net and starts trying to file warranty claims? Absolutely nothing. Have you even thought about that?
My claim makes no such assumptions. The inertia of the companies providing the service started out as a symptom of the IE-domination problem, but has now become a very real and integral part of the total problem. But first things first. We need to address the root cause, i.e. IE-by-default, before any permanent fix at the level of the service provider is going to have a chance of happening, and more importantly, of sticking.
You are making it ever more apparent that you are not actually one of us folks in the trenches fighting and reporting on this battle. In fact, it seems that you want to deny that there *is* still a battle at all, because Chrome (mostly) works OK for you on your home desktop.
Edit: BTW, OSNews.com's textarea widget for editing a post is only 2 lines high on my webkit based browser. So I suppose I am posting on a site which is, itself, a part of the problem.
Edited 2009-06-12 17:20 UTC