In keeping with fairness, a lot of the problem is not coming from Microsoft. Remember, this is the company that always wants everyone to upgrade to the newest thing as soon as it comes out, which is why patching a Windows machine will always inundate you with "upgrade to IE9 now!) dialog boxes. The truth of the matter is that big, slow moving entities--most specifically, the federal government and financial institutions--bought into Microsoft hook, line, and sinker back in the 90s, when they finally started the move off mainframes and token ring to PCs and Ethernet. These are the people who specifically coded for a certain browser, and have been stuck upgrading legacy code.Love it. Though to be fair, it should be Microsoft paying for all the extra coding and troubleshooting required by IE7, not the end user.
I was going to add health care providers to the "scold list", along with the federal government and financial institutions. Then, I remembered that most hospitals are so far back in the IT stone ages that they still have paper medical records and green or orange screen mainframes. Four years back, I interviewed for a company that was going to transition Fairfax Hospital from IBM mainframes and OS/2, running on token ring. One of the holdups? They'd have to transition from the dot matrix printers that you can't get drivers for, but they needed impact printers for the carbon paper medical records. Seriously, I cannot believe how far in the past that place is, and it is considered to have one of the best children's care units in the country.One of my sites (for a hospital) still has 15% of visitors that use IE using IE7. they are getting a new site next year.
I hadn't considered them. I never thought they even used computers. :ugh: Good point.Wirelessly posted dio
Narren, you have been out of the states too long. Can't you picture a couple of old folks on their dusty old Pentium III, forwarding their tea party emails to all their friends and family? Those are the people on IE7.