I encourage you to google (er, sorry, you probably use Bing!) about “NSS labs” and read about the accusations and questions regarding their credibility, as well as considering the general low credibility of paid studies.

Lastly, my main gripe against IE isn’t even its “safety” or security any more; it’s their poor conformance to web standards and their monopolistic behavior in the past that helped to crush competitors.

How much evidence does it take till you can admit that IE9 is really secure. You should be encouraging EVERYONE to use IE9 to minimize getting compromised.

Since we didn’t focus on IE we were able to cover more content that we would not have had otherwise. To those who are saying that makes me less employable I would disagree. I am working on a site for a group at the UW that (if I say so myself) looks fucking fantastic in every other browser. I just started testing it in IE and it looks like all of my time and data was given to the browser, which then had a seizure on it and gave it back.

But seeing as how Marty taught us standards and not hacks I can figure out how to fix it. I’m going to be adding a separate css sheet for only IE. That took me all of 2 minutes to google, and if we had covered how to handle each incarnation of that browser I would have missed out on a lot of the stuff that I have just been using. Besides, his class is mostly for beginners and it covers a lot more than html and css. The timing just doesn’t work to have a week or however much would be needed to cover every way that IE might render your page differently and how to fix it

If someone is at the level where their living depends on their ability to code and design, they should be able to figure out how to deal with something like this on their own. When we are all starting out, we need to learn the rules not the exception. Thanks to Marty I know what I need to make websites.

All I need now is the patience to rework my appearance every time IE rears it’s ugly head.