casey.o said:
I dont know what's been going on lately on Microsoft's website, but it's
not good for older browsers. Several times in recent days, I've ended
up on a MS site, to read an article or something, and since I'm using
Win98 and the limited browsers for it, which are old browsers, I am
finding the browsers completely freezing up, if I have java script
enabled.
The main problem with using the older browsers, which are all that will
operate on Win98, is script based. But I never had problems on
microsoft.com until very recently. I normally try to keep java script
disabled, which many sites bitch about, but tough shit, let em
bitch.....
Java scripts tend to make browsers run real slow or do other odd things.
But it seems the moment I get on MS's site lately, if JS is turned on,
my browsers just lock up tight. These are mozilla based browsers.
(firefox and k-meleon).
I've already seen messages from several web site saying they will no
longer support IE6. Apparently there are features or functions in later
versions that are required to now properly view their site. Since my
experience is just 1 sample of several sites demanding later versions of
IE then the aggregate of all users encountering such declaration is a
much larger total. It's not just Microsoft that is moving to up the
baseline for the minimum version of web browsers that they will support.
Lots of sites are doing that. IE6 is 13 years old! You thought sites
would stagnate? The only constant in the universe is things change.
I've seen some sites now declaring that IE8 is the minimum they will
support. They want to improve their site but still have to support a
range of web browser versions to encompass the majority of their
visitors. They realize they'll lose some visitors by upping the minimum
version for the client but they also realize that is a dwindling number
of visitors, so small that it won't impact the site's purpose. There
are still some folks using Lynx but sites don't care that they cannot be
fully viewed using a text-only web browser.
Most marketshare sites showing which version of Windows has how much
share of the Windows deployments don't even show Windows 98. That's
because it's so tiny that you couldn't see the ultra thin line
representing far under 0.1% marketshare. No one is going to waste their
time making sites compatible with that old OS. Internet Explorer 6 is
down to just 4.47% of the web browser marketshare (of just IE, even less
if you add in all the other web browsers). Again, such a small remnant
community that sites lose nearly nothing dropping support for that old
web browser version and moving on to improve their sites with features
supported by newer versions of web browsers.
The base version of IE that was included in Windows 98 was IE5? The
latest version you can install on Windows 98 is IE6. That means you
cannot install IE7, and later, on Windows 98. I don't what are the max
versions of Firefox and Chrome that you can install on Windows 98;
however, maybe you already have those. As new features become available
in web servers that expect some of them to get supported in later
versions of web browser clients then the baseline of where sites cutoff
support for older versions of clients will rise.
As for Javascript, older web browsers also make it run a lot slower. If
you checkout the web browser benchmarks over the last half dozen years,
or more, each new version of each web browser typically results in a
boost in performance in interpreting and executing Javascript. Yes,
sites have added more Javascript to their web pages, especially for
sites that like to use dynamic pages altered by client-side scripts
rather than have their server do that with server-side scripts, so
they've gotten slower; however, web browsers have sped up a lot more
than pages have enlarged their scripts to slow down.
For really old web browser versions, their interpretation and execution
speed of Javascript is so slow that sites that have upped the volume of
scripts in their web pages will makes those old web browsers take eons
to run them. In fact, the script may be so large (when compared to what
those old web browsers expected back in their heyday) that they will
probably timeout after 5 minutes (or "hang" as you noted but you didn't
say how long you waited). If you put an old Ford Model T (top speed of
45 mph under ideal conditions on a flat smooth road) in a Formula 500
race (~130 mph), the spectators would be laughing pretty loud plus it
wouldn't even be allowed on the track because it would be a severe
hazard to the other racers.