<?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: IE6 and the Starving Artist</title>
	<atom:link href="http://www.vertstudios.com/blog/ie6-starving-artist/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vertstudios.com/blog/ie6-starving-artist/</link>
	<description>Web design and development resources.</description>
	<lastBuildDate>Sun, 05 Feb 2012 01:37:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: There Was A Funeral For IE6, So Why Are We Still Designing For It? &#124; Blondish.net</title>
		<link>http://www.vertstudios.com/blog/ie6-starving-artist/comment-page-1/#comment-66</link>
		<dc:creator>There Was A Funeral For IE6, So Why Are We Still Designing For It? &#124; Blondish.net</dc:creator>
		<pubDate>Sat, 20 Mar 2010 10:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcculloughdesigns.com/blog/?p=228#comment-66</guid>
		<description>[...] is not just about integrity as said in Joseph McCullough&#8217;s article IE6 and the Starving Artist, it is about making people aware of how much safer it is to surf without a faulty browser. Funny [...]</description>
		<content:encoded><![CDATA[<p>[...] is not just about integrity as said in Joseph McCullough&#8217;s article IE6 and the Starving Artist, it is about making people aware of how much safer it is to surf without a faulty browser. Funny [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Plague of IE6: Throw the Monkey into the River! - Montana Programmer</title>
		<link>http://www.vertstudios.com/blog/ie6-starving-artist/comment-page-1/#comment-65</link>
		<dc:creator>The Plague of IE6: Throw the Monkey into the River! - Montana Programmer</dc:creator>
		<pubDate>Thu, 18 Mar 2010 15:14:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcculloughdesigns.com/blog/?p=228#comment-65</guid>
		<description>[...] McCullough from mcculloughdesigns.com wrote a great article on the concept that the life of IE6 is up to web developers. Below is a quote from that article: Some developers will see a problem in IE and automatically [...]</description>
		<content:encoded><![CDATA[<p>[...] McCullough from mcculloughdesigns.com wrote a great article on the concept that the life of IE6 is up to web developers. Below is a quote from that article: Some developers will see a problem in IE and automatically [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph McCullough</title>
		<link>http://www.vertstudios.com/blog/ie6-starving-artist/comment-page-1/#comment-63</link>
		<dc:creator>Joseph McCullough</dc:creator>
		<pubDate>Wed, 10 Mar 2010 01:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcculloughdesigns.com/blog/?p=228#comment-63</guid>
		<description>&lt;a href=&quot;#comment-67&quot; rel=&quot;nofollow&quot;&gt;@Cre8ive Commando&lt;/a&gt;
I understand that. That&#039;s actually the entire point. You can either make the client happy or help progress the web. If you eliminate the product, you eliminate the audience, and vice versa. But that would take the sacrifice of paychecks. Medieval artists adhered to the commands of their &quot;clients&quot; (in this case the Church Authority) to draw the Baby Jesus like an Ooompa Loompa, and consequently forgot how to draw a person in proper proportion. I don&#039;t see how we&#039;re immune from the same fate.

If IE6 hacks weren&#039;t so semantically ridiculous and counterintuitive, it wouldn&#039;t be a problem. But keeping them around is causing web coding to make less sense and operate less efficiently.</description>
		<content:encoded><![CDATA[<p><a href="#comment-67" rel="nofollow">@Cre8ive Commando</a><br />
I understand that. That&#8217;s actually the entire point. You can either make the client happy or help progress the web. If you eliminate the product, you eliminate the audience, and vice versa. But that would take the sacrifice of paychecks. Medieval artists adhered to the commands of their &#8220;clients&#8221; (in this case the Church Authority) to draw the Baby Jesus like an Ooompa Loompa, and consequently forgot how to draw a person in proper proportion. I don&#8217;t see how we&#8217;re immune from the same fate.</p>
<p>If IE6 hacks weren&#8217;t so semantically ridiculous and counterintuitive, it wouldn&#8217;t be a problem. But keeping them around is causing web coding to make less sense and operate less efficiently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cre8ive Commando</title>
		<link>http://www.vertstudios.com/blog/ie6-starving-artist/comment-page-1/#comment-62</link>
		<dc:creator>Cre8ive Commando</dc:creator>
		<pubDate>Wed, 10 Mar 2010 00:56:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mcculloughdesigns.com/blog/?p=228#comment-62</guid>
		<description>Trashing IE6 hacks would be great but at this time I don&#039;t really think it&#039;s realistic. Bottom line is, your client won&#039;t notice an IE6 hack, but they will notice if their website doesn&#039;t display properly when they view it on their dads old computer.</description>
		<content:encoded><![CDATA[<p>Trashing IE6 hacks would be great but at this time I don&#8217;t really think it&#8217;s realistic. Bottom line is, your client won&#8217;t notice an IE6 hack, but they will notice if their website doesn&#8217;t display properly when they view it on their dads old computer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

