151–160 of 185 posts
Just checked the analytics on a non-IT website: IE represents 10.45% Out of that: IE6 .28% IE7 2.03% IE8 19.81% IE9 16.57% IE10 16.15% IE11 45.13%
Here's bloomberg.com: IE represents 25.00% IE6 0.11% IE7 3.20% IE8 34.39% IE9 32.94% IE10 16.48% IE11 12.87%
I do mostly contract work in the U.S. for state and local governments. The RFP's (Request for Proposals) always say something about using HTML5, responsiveness and the latest web standards. And sometime shortly after (and sometimes before) project kickoff we always see that a large percentage of their employees are using IE8 and we have to support it. I make a point of describing in detail what kind of resources will…
While I commend you for finding a way to communicate to your clients in a way that allows you to not develop for IE8, you're not really being truthful. You can use "HTML5" with IE8 as part of html5shiv.js of course and IE8 doesn't need to be responsive - its a desktop browser. In most cases you can almost certainly deliver an IE8 solution without a lot of extra work.
As others have pointed out, IE6 isn't dead yet. Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. And I'm afraid a lot of us have been complicit in the unusually long life of this dreadful monster, as well as of its just-as-dreadful offspring, IE8. By "us" I mean everyone who has ever developed a website in the last fe…
> If we really want to kill IE[6-8], we need to do something more drastic, and do so with extreme prejudice. How about we all agree upon a certain date on which we intentionally break our websites and services for IE6 users? Maybe for a blog, but I'm not telling 10%+ of my customers to piss off. If the cost of supporting them outweighs the value of their business then I won't support them any more. But I would never…
IE6 is certainly nowhere near as capable as modern browser but if you don't need fancy HTML and whamodyne JS then maybe it's not such a handicap after all?
Earlier quoted context omitted.
You might also like to run metrics as to how those same IE6 users evangelize your service. They might be really good at word of mouth, or at recommending other enterprise-level customers in via the golf course. Or - more realistically - you could actually consider 10% of your customers a large, valuable chunk whatever the ROI and accommodate them. Your choice.
Well, they're not valuable if the ROI is negative.
As most sites follow some kind of 80/20 rule, be careful to dismiss a small percentage of users if they fall in the critical 20%.
Then again, if you have data that shows IE6 users are just parasites, get rid of them.
Earlier quoted context omitted.
> If we really want to kill IE[6-8], we need to do something more drastic, and do so with extreme prejudice. How about we all agree upon a certain date on which we intentionally break our websites and services for IE6 users? Maybe for a blog, but I'm not telling 10%+ of my customers to piss off. If the cost of supporting them outweighs the value of their business then I won't support them any more. But I would never…
These people might be using Microsoft software, but it would be a stretch to call them Microsoft customers. When was the last time they actually coughed up any cash? Besides, this is a bed Microsoft made, so they need to lie in it. The longer people stay with XP / IE 6-8, the worse the Internet gets for everyone. M$ is the only company that can do anything about it, and it's in their best interest to, so they just ne…
As others have pointed out, IE6 isn't dead yet. Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. And I'm afraid a lot of us have been complicit in the unusually long life of this dreadful monster, as well as of its just-as-dreadful offspring, IE8. By "us" I mean everyone who has ever developed a website in the last fe…
Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. No, two things: i) It's not about being stubborn. Companies have invested a lot of money and time to run critical applications. Even if they have the money the risk of migration is high. ii) They have already migrated to newer browsers! they just run IE6 side by side wi…
As others have pointed out, IE6 isn't dead yet. Any person or business that is stubborn enough to use IE6 nowadays is probably also stubborn enough to keep using Windows XP for another year or ten. And I'm afraid a lot of us have been complicit in the unusually long life of this dreadful monster, as well as of its just-as-dreadful offspring, IE8. By "us" I mean everyone who has ever developed a website in the last fe…
Earlier quoted context omitted.
> If we really want to kill IE[6-8], we need to do something more drastic, and do so with extreme prejudice. How about we all agree upon a certain date on which we intentionally break our websites and services for IE6 users? Maybe for a blog, but I'm not telling 10%+ of my customers to piss off. If the cost of supporting them outweighs the value of their business then I won't support them any more. But I would never…
I keep trying to imagine developers deliberately breaking their source code to fail in Bill Joy's vi to force users to upgrade to vim. IE6 is certainly nowhere near as capable as modern browser but if you don't need fancy HTML and whamodyne JS then maybe it's not such a handicap after all?
As a dev I have been trying to convince the project managers of the following theory of people who use IE6/7/8. They must fall into one the following categories 1. Windows XP, which does not allow them to upgrade to IE9 AND do not know that other non-sucky browsers exist 2. They work for a company that requires IE8 3. They are masochists who love pain) 4. They are sadists who enjoy dealing out pain to Web developers.…
In regards to your first solution, I keep going back and forth on whether or not it's professional to add a conditional warning that detects an old browser and explains the upgrade process. I know there are some scripts you can throw on your sites that automatically do this, but I'm not sure if that's a good idea.