<?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: Why we&#8217;re stuck with IE6 for the forseeable future</title>
	<atom:link href="http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html</link>
	<description>Michael Krotscheck's insights, ideas, and inspirations about web technology, life, and the kitchen sink.</description>
	<lastBuildDate>Fri, 03 Feb 2012 05:12:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Alec</title>
		<link>http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html/comment-page-1#comment-858</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Sat, 09 May 2009 01:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html#comment-858</guid>
		<description>Great analysis. But at least we are able to drop IE 5.5. Surely you remember coding around that dog...

IE6 can be coded into relatively graceful obsolescence. The visitors will see enough of the site that they can live with the broken edges.</description>
		<content:encoded><![CDATA[<p>Great analysis. But at least we are able to drop IE 5.5. Surely you remember coding around that dog&#8230;</p>
<p>IE6 can be coded into relatively graceful obsolescence. The visitors will see enough of the site that they can live with the broken edges.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krotscheck</title>
		<link>http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html/comment-page-1#comment-804</link>
		<dc:creator>Michael Krotscheck</dc:creator>
		<pubDate>Thu, 29 Jan 2009 04:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html#comment-804</guid>
		<description>Oh, I know. It&#039;s just my own subtle rebellion against outdated browsers :)</description>
		<content:encoded><![CDATA[<p>Oh, I know. It&#8217;s just my own subtle rebellion against outdated browsers <img src='http://www.krotscheck.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html/comment-page-1#comment-803</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Wed, 28 Jan 2009 16:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/11/23/why-were-stuck-with-ie6-for-the-forseeable-future.html#comment-803</guid>
		<description>Hey! These pages don&#039;t scroll in IE6! What gives?</description>
		<content:encoded><![CDATA[<p>Hey! These pages don&#8217;t scroll in IE6! What gives?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

