IMHO It isn't so much legacy code that brought IE down ... it's all the undocumented backdoor crap M$ leaves in place in all its software which they use to exploit the "power" of their program (ie, avoiding the spaghetti code) while publishing weaker, slower links (that go through the spaghetti code) to non-M$ programmers resulting in 3rd party programs that aren't as fast/efficient/whatever thus "proving" the superiority of M$ programming. Then, when some smart guy comes along and finds some of these backdoors, M$ runs around screaming, "Virus, virus, the sky is falling, oh woe woe woe!!" Gimmie a break. With M$ it will always be about being "superior" (ie, more profitable to M$). There wouldn't be any alternatives today if the hardcore amongst us hadn't been willing to swim uphill against the corporate sheeple (tied to IE by fiat and force) to support actual standard-compliant browsers like Firefox/Chrome/etc..
"Everyone likes to rip on IE, but IE 11 is actually not all that bad." ~ Spac3nerd
LOL Now, if M$ hadn't bound IE11 so closely to the operating system (or is IE the next WOS? hmmm... 3
), perhaps it would run on earlier operating systems (like a normal standalone program). LOL If M$ were actually serious about supporting the standard, it could have easily "read the book, implement the code, read the book, implement the code" better than anyone. Could have. The real solution to the issue is to:
<!DOCTYPE html>
<html lang="en"> /* sue me I'm biased */
<head>
<meta charset="utf-8">
...
<title></title>
<style type="text/css">
<!--
body {
...
}
-->
</style>
<!--[if IE]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
...
</body>
</html>
thus letting someone else deal with the IE headache.
@firefoxx04: I'm with you dude(ette?). If the customer doesn't have paid-subscription-based anti-bugware installed and up-to-date, I have no compunction at all taking their money to reformat the hard drive and re-install their software.
@silverblue in re to Firefox crashing ... yeah. They've become a modern example of bloatware but unfortunately it didn't include robust memory management. Under 32-Bit XP Pro with the requisite 3.5GB RAM, Firefox slows and then crashes about the time memory usage hits 6-7 GB (obviously by then the HD is singing like a canary). Same computer running Chrome will happily hit 10-12 GB (with the HD chatter) but it doesn't crash ... the system just runs slower and slower until one gets sick of waiting for the screen to re-paint and restarts the computer. Now, you say that had to be that screwed up old XP. Ehhh! Yes, I am an XP fan boy. No, nothing in Win7 or 8 has convinced me they are any better (and frankly from a power user POV they are orders of magnitude clumsier but that's another story). Next system was an i7-based Win7 Pro 64-Bit monster with 16 GB. LOL Firefox still dies about 6-7 GB (but at least the HD wasn't chewing up head-motion hours). And Chrome can still happily open a dozen windows (each with a dozen or so tabs open) -- 8-10 GB worth -- and keep on going. Let's face it, being able to court the best with a huge pocketbook will almost always trump any volunteer effort. That's just the way it is. That's why M$ is still the powerhouse that it is. Well, that and most corporate systems being held hostage by them as well. LOL
Facebook
Twitter
Instagram