When Internet Explorer 6 came out in 2001, it was a huge step forward for the browsing world. Sadly, while the long-living browser still commands a strong contingent of users, it has outlived its welcome for at least 5 years. Nowadays, the nearly 8 year old browser still continues to be a thorn in side of web developers. When I redesigned my site this past January, I was unwilling to commit to the time it would take to make IE6 fully compatible with the design and unorthodox elements on the site. I had a choice of allowing visitors using IE6 to have a downgraded version of the site (which would take time in and of itself to implement) or to block them altogether. I chose the latter and I am writing why I think it is a reasonable decision. Continue reading “Why I Block IE6 and Why You Should Consider Doing the Same”
As a former front-end developer, I know the horrors of building HTML/CSS sites that work across all browsers. Frankly, the whole cross-browser conundrum was one reason why I got out of it a year or two ago. While I may not get paid to build static websites anymore, I obviously am still vulnerable to these problems with the sporadic interface/visual revamps I make to this blog and other minor web projects I take on. As the months go by, I see my ability to (reliably) develop HTML/CSS that will work in older browsers. That is why I really like the notion of what the Save the Developers campaign is trying to do.