HTML5 CSS3 IncompatibilitiesRemember having to insert the following into your head tag to help fix the lack of support IE8 has for html5 tags and CSS3 properties? (or using Modernizer)
<!--[if lt IE 8]> <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script> <script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script> <![endif]-->
Missing functionsRemember having to use es5-shim because IE8 did not implement lastIndexOf, map, filter, every, forEach, etc. functions?
Security VulnerabilitiesDid you know the IE8 has over 500 known security vulnerabilities? (that will never get fixed)
IE8's continued reliance on ActiveX makes it vulnerable to the core.
Unforgiving ParserBack in the days of IE5, IE was very forgiving when it came to HTML syntax.
I'm not saying that I approve of a lax enforcement of standards, but I do recall how quickly a web developer could crank out a web application when the user base were all IE users. Not so for IE8.
In many cases, IE8 would make your site break, even if it were coded perfectly.
Good bye, IE8. (and good riddance!)
p.s. Unbelievably, IE8 was actually somewhat better than IE7.
This work is licensed under the Creative Commons Attribution 3.0 Unported License.