<?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: Internet Explorer 8 round-up</title>
	<atom:link href="http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/</link>
	<description>A web log about web development and internet culture with frequent detours into other stuff.</description>
	<lastBuildDate>Fri, 12 Mar 2010 07:01:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rashid Z. Muhammad</title>
		<link>http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/comment-page-1/#comment-90570</link>
		<dc:creator>Rashid Z. Muhammad</dc:creator>
		<pubDate>Wed, 23 Jan 2008 19:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/#comment-90570</guid>
		<description>Compatibility vs. compliance is the classic trade off and Microsoft&#039;s position has been the same for 30 years. So has Apple&#039;s. And I have to say that breaking quicktime functionality in my $1000 copy of Final Cut Pro with a QT update that Apple kept bothering me to get (6.5 to 7.0) pisses me off a lot more than adding meta tags to my web apps.

This isn&#039;t to take shots at Apple but just to say that, from my vantage point at least, this issue really is a catch 22 that will burn a ton of people either way.</description>
		<content:encoded><![CDATA[<p>Compatibility vs. compliance is the classic trade off and Microsoft&#8217;s position has been the same for 30 years. So has Apple&#8217;s. And I have to say that breaking quicktime functionality in my $1000 copy of Final Cut Pro with a QT update that Apple kept bothering me to get (6.5 to 7.0) pisses me off a lot more than adding meta tags to my web apps.</p>
<p>This isn&#8217;t to take shots at Apple but just to say that, from my vantage point at least, this issue really is a catch 22 that will burn a ton of people either way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tiffany</title>
		<link>http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/comment-page-1/#comment-90568</link>
		<dc:creator>tiffany</dc:creator>
		<pubDate>Tue, 22 Jan 2008 23:44:06 +0000</pubDate>
		<guid isPermaLink="false">http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/#comment-90568</guid>
		<description>I agree with you and Jeremy: it makes no sense to have opt-in to standards compliance. And as someone said (I think it was on van Kesteren&#039;s post), everything is already broken because of IE&#039;s special way of implementing stuff. 

I think Microsoft has to go this route, though, because if a web site breaks, the user and developer will blame Microsoft instead of their own code. 

For example, one of the big complaints I heard about Netscape 4 among those who preferred IE was that sites just &quot;look right&quot; and &quot;work better&quot; in IE 4 (or maybe it was IE 5). What those folks didn&#039;t know was that the HTML was crap and IE handled crap code better.

Rather than risk being seen as a broken browser by folks who don&#039;t know better (average web user, slack a** developers with old skills) and losing market share, MS is choosing to support bad code. 

I think it&#039;s smart for Microsoft&#039;s business. It&#039;s an intelligent way to make the best of a bad situation and maintain backwards compatibility. 

That said, I&#039;m annoyed about &lt;em class=&quot;b&quot;&gt;still&lt;/em&gt; having to do something special so that my sites still look and behave sensibly in a Microsoft browser -- and not just behave sensibly, but &lt;em&gt;behave as the specification(s) say they should&lt;/em&gt;. I think the execution of it sucks big fat donkey balls.</description>
		<content:encoded><![CDATA[<p>I agree with you and Jeremy: it makes no sense to have opt-in to standards compliance. And as someone said (I think it was on van Kesteren&#8217;s post), everything is already broken because of IE&#8217;s special way of implementing stuff. </p>
<p>I think Microsoft has to go this route, though, because if a web site breaks, the user and developer will blame Microsoft instead of their own code. </p>
<p>For example, one of the big complaints I heard about Netscape 4 among those who preferred IE was that sites just &#8220;look right&#8221; and &#8220;work better&#8221; in IE 4 (or maybe it was IE 5). What those folks didn&#8217;t know was that the HTML was crap and IE handled crap code better.</p>
<p>Rather than risk being seen as a broken browser by folks who don&#8217;t know better (average web user, slack a** developers with old skills) and losing market share, MS is choosing to support bad code. </p>
<p>I think it&#8217;s smart for Microsoft&#8217;s business. It&#8217;s an intelligent way to make the best of a bad situation and maintain backwards compatibility. </p>
<p>That said, I&#8217;m annoyed about <em class="b">still</em> having to do something special so that my sites still look and behave sensibly in a Microsoft browser &#8212; and not just behave sensibly, but <em>behave as the specification(s) say they should</em>. I think the execution of it sucks big fat donkey balls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j. brotherlove</title>
		<link>http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/comment-page-1/#comment-90567</link>
		<dc:creator>j. brotherlove</dc:creator>
		<pubDate>Tue, 22 Jan 2008 20:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://tiffanybbrown.com/2008/01/22/internet-explorer-8-round-up/#comment-90567</guid>
		<description>And where do you weigh in on the subject? The discussion (dare I say &lt;em&gt;outcry&lt;/em&gt;) over IE8&#039;s compatability is already making my head hurt. But I believe IE8 should render compliant IE8 &quot;out the box&quot;. Having to insert code to tell it to behave &lt;em&gt;the way it was built to&lt;/em&gt; doesn&#039;t even sound right. Then again, whichever way this goes, a bunch of sites will need tweaking.</description>
		<content:encoded><![CDATA[<p>And where do you weigh in on the subject? The discussion (dare I say <em>outcry</em>) over IE8&#8217;s compatability is already making my head hurt. But I believe IE8 should render compliant IE8 &#8220;out the box&#8221;. Having to insert code to tell it to behave <em>the way it was built to</em> doesn&#8217;t even sound right. Then again, whichever way this goes, a bunch of sites will need tweaking.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
