Leave a Reply
11 Responses to “Seminary and IE 6 Notifications”
Tweets that mention Seminary and IE 6 Notifications | ChurchIT -- Topsy.com
[...] This post was mentioned on Twitter by 8Bit, ChurchInfoTech. ChurchInfoTech said: Seminary and IE 6 Notifications http://bit.ly/aojKiM [...]
- 4,481 feedburner + twitter followers
Browser Share - IE Still Reigns, But Not For Long... 
I’m glad to see so many organizations taking this stand against antiquated browsers. I don’t even design/develop with IE6 in mind anymore (unless a client asks — and PAYS — for it).It’s time to leave these browsers that are more than 10 years old behind and embrace the future.
Love me some CSS3.
Haven’t seen you in a while! How are you doing? I’d love for you to consider contributing more; you’ve got some obvious talent!
Have a great weekend!
I learnt web design in the early Noughties; ardently hand-coding HTML & CSS in an era of IE6. My position has always been that your audience should not be siloed by the browser, context or device they use to access your website or web app.
Writing valid and semantic code is the easiest way to make your product accessible to the largest possible audience. That said, I am an equally strong proponent of “progressive enhancement” and employing the latest generation of HTML5 & CSS3 features.
It has always been best practice to use the most update version of coding languages – e.g. HTML5 & CSS3. This is due to the fact that they usually afford you instant backwards compatibility for the vast majority of their features.
Therefore, denouncing support for IE6 does nothing but proclaim your own laziness.
(Don’t get me wrong; I hate IE6 as much as the rest of the web community. But when it costs us nothing to support it, we have no right to demand its exclusion.)
but it does cost us something. time, money, and energy. that’s not laziness, that’s being a good steward of our resources.
sure, it’s a give and take, but the web is moving away from it’s outdated forms.
The mere act of creating a “bells and whistles” HTML5 & CSS3 website, also leaves you with something that users of IE6 can still access. You can argue the semantics of “supporting” IE6 until you’re blue in the face, but to my mind graceful degradation is still a form of “supporting”.
My point is that it costs you no extra time, during the planning phase, to bear in mind how your website will degrade for older browsers. This is essential knowledge for all coders. Remember, we already have to consider cross browser compatibility.
Resist the temptation to needlessly filter and ring-fence your audience. If you feel you can justify dropping IE6, isn’t it hypocritical to not also drop support for Opera, Flock and other small browsers?
It blows my mind that organizations & individuals fail to update to new software. I heard that somewhere around 40% of browsers still in use are IE6… why do people hesitate to update?
laziness, education, ignorance… ad nauseum…
“Therefore, denouncing support for IE6 does nothing but proclaim your own laziness.”
If Google no longer supports IE6 (January 2010), what makes you think a small shop or sole proprietor can? I don’t think it is laziness, I would argue that it is a necessity. In order to offer a service for a cost the client won’t scoff at, you have to draw the line.
http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html
“I heard that somewhere around 40% of browsers still in use are IE6… why do people hesitate to update?”
I don’t think it is that high. I’ll look around for a stat. But on my site, it is more like 4-6%.
If you are using JQuery, try this in your apps.
http://jreject.turnwheel.com/
We are doing the same thing at my church once we launch our new design in the late summer. IE6 is gone and should be by now.