<?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: Google Wave: google frustrated with Internet Explorer?</title>
	<atom:link href="http://blog.ssims.co.uk/index.php/2009/11/google-wave-google-frustrated-with-internet-explorer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ssims.co.uk/index.php/2009/11/google-wave-google-frustrated-with-internet-explorer/</link>
	<description>Software, Computing and Web technology discussion</description>
	<lastBuildDate>Thu, 12 Aug 2010 15:07:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ssims</title>
		<link>http://blog.ssims.co.uk/index.php/2009/11/google-wave-google-frustrated-with-internet-explorer/comment-page-1/#comment-565</link>
		<dc:creator>ssims</dc:creator>
		<pubDate>Thu, 17 Dec 2009 21:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ssims.co.uk/?p=328#comment-565</guid>
		<description>So it seems that in fact the IE add-on essentially allows IE to interpret pages in the same way Chrome does. While my original speculation about its operation was wrong, nevertheless my suspicion the &#039;fix&#039; was a bad idea seems to be correct - instead of treating one target platform very differently they are essentially opting to doctor it so they can ignore its quirks. In my opinion this entirely misses the point that different users may have very different browsers, and they should all to an extent be supported. What&#039;s the difference between enforcing a user installs a fix that makes IE behave like Chrome, and enforcing that they install Chrome itself? The answer is very little.</description>
		<content:encoded><![CDATA[<p>So it seems that in fact the IE add-on essentially allows IE to interpret pages in the same way Chrome does. While my original speculation about its operation was wrong, nevertheless my suspicion the &#8216;fix&#8217; was a bad idea seems to be correct &#8211; instead of treating one target platform very differently they are essentially opting to doctor it so they can ignore its quirks. In my opinion this entirely misses the point that different users may have very different browsers, and they should all to an extent be supported. What&#8217;s the difference between enforcing a user installs a fix that makes IE behave like Chrome, and enforcing that they install Chrome itself? The answer is very little.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
