Or are stuck on dialup and flat out can’t afford it. People often lose sight of the fact that in America we have massive areas where a high speed connection is 768/128 that runs $100/mo or more… and area’s where 33.6 dialup is still a good day – take Coos County here in New hampshire. I travel 80 miles north and there is no such thing as broadband! The Dakota’s, most of the deep Appalachians and Rockies – we’re talking large swaths where the only thing you might be able to get for broadband is the ridiculously overpriced “hughes-net” rubbish.
Downloading even a modern browser is impractical at those speeds.
You also have the poor. Not everyone can afford to drop a grand or two every three years – I know a lot of people still using Windows 98 boxes… Hell at a friend of mine’s work she’s on a Win98 machine that wipes itself nightly back to just IE6 and hyperterminal – the latter of which is still used to connect into their client database on a bloody PDP-11. “It works, why spend money we don’t have to?”. (I’m more than aware of this as I’m the only person in town qualified to SERVICE one of those)
Stevie is also quite correct in pointing out corporate users. Microsoft did something really innovative with Trident when they released IE 5 – they documented the entire engine API and allowed anyone to use it to build their software – letting you leverage HTML and CSS to build your application UI’s… and I have to laugh at the FLOSS whackjobs who badmouthed that while promoting the use of XUL runner; or how “HTML behaving as full desktop applications” is some miraculous new idea for IE 10.
MANY of the in-house crapplets tossed together with Trident, most of them written in Visual Basic, break if you so much as THINK about upgrading to a newer IE and don’t work in other browsers. Some of them even break if those other browsers steal the default program status. We’re talking ten and twelve year old software that you tell the boss “we need to update it” they’re going to ask “why, it’s working just fine with the software we have.”
… and saying “Well, some web developers are too lazy to support it and want to use a bunch of fancy bells, whistles and gee ain’t it neat animooted effects that have nothing to do with content delivery” isn’t going to fly as an answer! Frankly that is what it boils down to in many cases as if people would pull their damned heads out of 1998’s backside, practicing separation of presentation from content, semantic markup, built the sites using progressive enhancement with accessibility in mind from the start, they wouldn’t have these issues of at least making the pages WORK in legacy IE. If you build using “progressive enhancement” should said bells, whistles and “gee aint it neat” bull are unavailable the site gets “graceful degradation”!
They don’t have to be pixel perfect, they don’t have to have all those fancy bells and whistles – but they should still be at least usable – WITHOUT “HTML 5 shim” idiocy, WITHOUT “IE conditional comments” bloating out the markup to cover up bad site-building methodologies, and without any real extra effort on building the site!!!
But of course people will just continue sleazing out code as fast and half-assed as possible who cares if it works anywhere but their pet browser at their pet resolution and screen size, much less how much it ends up costing in the long term for hosting, loss of potential clients via a high bounce rate, needlessly complex code that’s impossible to maintain much less debug, etc, etc, etc…