<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is it finally time to ditch IE6?</title>
	<atom:link href="http://karinne.net/2008/08/27/is-it-finally-time-to-ditch-ie6/feed/" rel="self" type="application/rss+xml" />
	<link>http://karinne.net/2008/08/27/is-it-finally-time-to-ditch-ie6/</link>
	<description>web non-sense : The online ramblings of a wife and mother who&#039;s passionate about web standards, music, jeeping and soccer.</description>
	<lastBuildDate>Tue, 09 Mar 2010 14:34:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Plant</title>
		<link>http://karinne.net/2008/08/27/is-it-finally-time-to-ditch-ie6/comment-page-1/#comment-876</link>
		<dc:creator>Michael Plant</dc:creator>
		<pubDate>Thu, 13 Nov 2008 00:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://karinne.net/?p=57#comment-876</guid>
		<description>I am definitely with you 100%. And in response to Jason sure, if you aren&#039;t trying to anything unique easy fixes suffice, but aren&#039;t we all tired of being forced to deal!  Toss it already! If your company still has you in that dinosaur then they are falling asleep at the wheel.

That&#039;s what makes web design such a great field to be in, everything keeps changing. And generally for the better so in my not so humble opinion &quot;I am sick of dealing with it.&quot; 

When you have to jump through hoops to find a working copy anymore it seems pretty silly to me. If I find myself having to download a quarterly copy of a Microsoft issued fake hard drive I think it&#039;s time the rest of the world catches up!  

We were discussing this today, a colleague of mine and I, both CSS Developers and we agree, mandatory upgrades! LOL

&lt;abbr&gt;&lt;em&gt;Michael PlantÂ´s last blog post..&lt;a href=&quot;http://michaelplant.info/uncategorized/character-encoding-issues-arrising-from-content-stored-in-a-sql-server-database/2008/10/23&quot; rel=&quot;nofollow&quot;&gt;Character Encoding issues arrising from Content stored in a SQL server database.&lt;/a&gt;&lt;/abbr&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>I am definitely with you 100%. And in response to Jason sure, if you aren&#8217;t trying to anything unique easy fixes suffice, but aren&#8217;t we all tired of being forced to deal!  Toss it already! If your company still has you in that dinosaur then they are falling asleep at the wheel.</p>
<p>That&#8217;s what makes web design such a great field to be in, everything keeps changing. And generally for the better so in my not so humble opinion &#8220;I am sick of dealing with it.&#8221; </p>
<p>When you have to jump through hoops to find a working copy anymore it seems pretty silly to me. If I find myself having to download a quarterly copy of a Microsoft issued fake hard drive I think it&#8217;s time the rest of the world catches up!  </p>
<p>We were discussing this today, a colleague of mine and I, both CSS Developers and we agree, mandatory upgrades! LOL</p>
<p><abbr><em>Michael PlantÂ´s last blog post..<a href="http://michaelplant.info/uncategorized/character-encoding-issues-arrising-from-content-stored-in-a-sql-server-database/2008/10/23" rel="nofollow">Character Encoding issues arrising from Content stored in a SQL server database.</a></em></abbr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://karinne.net/2008/08/27/is-it-finally-time-to-ditch-ie6/comment-page-1/#comment-556</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Thu, 25 Sep 2008 21:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://karinne.net/?p=57#comment-556</guid>
		<description>I believe that graceful degredation is the answer here. Yes IE6 is old but its popular. Its rediculous to think that you would close the door to 5% of your visitors, yet alone 20%+.

I find that between 1-2% of a projects development time is spent addressing IE6-7. Usually this is only a handful of CSS statements to correct minor issues. In the scheme of things this is not long at all.

It is asked above whether web designers should charge more for IE6. Isn&#039;t that a silly question? For me the time to develop IE6 is factored into the project costing but then again so is everything else.

Until the day comes when the cost of displaying a well rendered IE6 page exceeds that which the client can make from IE6 visitors it should be supported. After that a small message should be displayed. &quot;Internet Explorer 8 is now availible. Please upgrade now.&quot;

As for killing off the browser. Microsoft is already doing it one computer at a time. Vista is packaged with IE7. As XP fades away so will IE6. It will take as long as it takes. Punishing IE6 users in the meantime just doesn&#039;t seem fair.</description>
		<content:encoded><![CDATA[<p>I believe that graceful degredation is the answer here. Yes IE6 is old but its popular. Its rediculous to think that you would close the door to 5% of your visitors, yet alone 20%+.</p>
<p>I find that between 1-2% of a projects development time is spent addressing IE6-7. Usually this is only a handful of CSS statements to correct minor issues. In the scheme of things this is not long at all.</p>
<p>It is asked above whether web designers should charge more for IE6. Isn&#8217;t that a silly question? For me the time to develop IE6 is factored into the project costing but then again so is everything else.</p>
<p>Until the day comes when the cost of displaying a well rendered IE6 page exceeds that which the client can make from IE6 visitors it should be supported. After that a small message should be displayed. &#8220;Internet Explorer 8 is now availible. Please upgrade now.&#8221;</p>
<p>As for killing off the browser. Microsoft is already doing it one computer at a time. Vista is packaged with IE7. As XP fades away so will IE6. It will take as long as it takes. Punishing IE6 users in the meantime just doesn&#8217;t seem fair.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
