<?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: March</title>
	<atom:link href="http://ma.tt/2004/06/march/feed/" rel="self" type="application/rss+xml" />
	<link>http://ma.tt/2004/06/march/</link>
	<description>Unlucky in Cards</description>
	<lastBuildDate>Mon, 30 Jan 2012 18:53:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19904</generator>
	<item>
		<title>By: Anne</title>
		<link>http://ma.tt/2004/06/march/#comment-5112</link>
		<dc:creator>Anne</dc:creator>
		<pubDate>Thu, 17 Jun 2004 16:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5112</guid>
		<description>You might want to read &lt;a href=&quot;http://channel9.msdn.com/ShowPost.aspx?PostID=2366#2366&quot;&gt;the list of goals of the lead developer&lt;/a&gt;, more specifically, point 4.</description>
		<content:encoded><![CDATA[<p>You might want to read <a href="http://channel9.msdn.com/ShowPost.aspx?PostID=2366#2366">the list of goals of the lead developer</a>, more specifically, point 4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Distler</title>
		<link>http://ma.tt/2004/06/march/#comment-5111</link>
		<dc:creator>Jacques Distler</dc:creator>
		<pubDate>Thu, 17 Jun 2004 16:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5111</guid>
		<description>&lt;blockquote&gt;&lt;p&gt;[T]he stagnation of IE is not a resources problem, it is a strategic decision.&lt;/p&gt;&lt;/blockquote&gt;

I agree. As I said, they have &lt;em&gt;strong&lt;/em&gt; reasons not to change IE&#039;s behaviour in rendering existing web pages. Which means that modulo their interest in supporting new technologies (from XAML to MathML), they have no reason to &lt;em&gt;touch&lt;/em&gt; the existing engine.

This is the only plausible path for them to make significant changes in their engine, without breaking stuff.

As to the rich-client/web-app thing, MS is big enough to play both sides of the street, and knows that it &lt;em&gt;has&lt;/em&gt; to play both sides of the street, if it is going to ensure its own survival.</description>
		<content:encoded><![CDATA[<blockquote><p>[T]he stagnation of IE is not a resources problem, it is a strategic decision.</p>
</blockquote>
<p>I agree. As I said, they have <em>strong</em> reasons not to change IE&#8217;s behaviour in rendering existing web pages. Which means that modulo their interest in supporting new technologies (from XAML to MathML), they have no reason to <em>touch</em> the existing engine.</p>
<p>This is the only plausible path for them to make significant changes in their engine, without breaking stuff.</p>
<p>As to the rich-client/web-app thing, MS is big enough to play both sides of the street, and knows that it <em>has</em> to play both sides of the street, if it is going to ensure its own survival.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://ma.tt/2004/06/march/#comment-5110</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 17 Jun 2004 16:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5110</guid>
		<description>What I got out of the article was they&#039;re betting the farm on the rich client, and their biggest compitetor is web applications and potentially themselves if they increase IE&#039;s advanced DHTML ability, for example. Microsoft employs a lot of very smart people, and if the stagnation of IE is not a resources problem, it is a strategic decision.</description>
		<content:encoded><![CDATA[<p>What I got out of the article was they&#8217;re betting the farm on the rich client, and their biggest compitetor is web applications and potentially themselves if they increase IE&#8217;s advanced DHTML ability, for example. Microsoft employs a lot of very smart people, and if the stagnation of IE is not a resources problem, it is a strategic decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Distler</title>
		<link>http://ma.tt/2004/06/march/#comment-5109</link>
		<dc:creator>Jacques Distler</dc:creator>
		<pubDate>Thu, 17 Jun 2004 15:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5109</guid>
		<description>One of the key points of Joel&#039;s article is that not breaking backwards compatibility was a high priority at MS. You are &lt;em&gt;never&lt;/em&gt; going to see IE change its behaviour in a way that breaks existing web pages by the millions.

On the other hand, MS is bundling the MathPlayer 2.0 plugin (which brings &lt;code&gt;application/xhtml+xml&lt;/code&gt; and MathML support to IE/6) with Encarta. They already support rendering X(HT)ML for local pages. It would not be surprising at all if they decided that a more &quot;integrated&quot; approach would be beneficial to their plans for IE.

With a cleaner codebase, guaranteed well-formed input and no issues of maintaining backwards compatibility, it would be a &lt;em&gt;lot&lt;/em&gt; easier for them to support Standards. Anne&#039;s suggestion is unlikely, but not &lt;em&gt;wildly implausible&lt;/em&gt;.

And it fits with other things they are doing (unlike most other &quot;suggestions&quot; to the IE team).</description>
		<content:encoded><![CDATA[<p>One of the key points of Joel&#8217;s article is that not breaking backwards compatibility was a high priority at MS. You are <em>never</em> going to see IE change its behaviour in a way that breaks existing web pages by the millions.</p>
<p>On the other hand, MS is bundling the MathPlayer 2.0 plugin (which brings <code>application/xhtml+xml</code> and MathML support to IE/6) with Encarta. They already support rendering X(HT)ML for local pages. It would not be surprising at all if they decided that a more &#8220;integrated&#8221; approach would be beneficial to their plans for IE.</p>
<p>With a cleaner codebase, guaranteed well-formed input and no issues of maintaining backwards compatibility, it would be a <em>lot</em> easier for them to support Standards. Anne&#8217;s suggestion is unlikely, but not <em>wildly implausible</em>.</p>
<p>And it fits with other things they are doing (unlike most other &#8220;suggestions&#8221; to the IE team).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://ma.tt/2004/06/march/#comment-5107</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 17 Jun 2004 15:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5107</guid>
		<description>I don&#039;t know how Anne could read Joel&#039;s API article and then write about improving IE. It&#039;s not going to happen in &lt;em&gt;my&lt;/em&gt; lifetime.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know how Anne could read Joel&#8217;s API article and then write about improving IE. It&#8217;s not going to happen in <em>my</em> lifetime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Distler</title>
		<link>http://ma.tt/2004/06/march/#comment-5106</link>
		<dc:creator>Jacques Distler</dc:creator>
		<pubDate>Thu, 17 Jun 2004 15:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://photomatt.net/2004/06/17/march/#comment-5106</guid>
		<description>Deliberately invalidating (more importantly, rendering ill-formed) every page of your site is a &lt;em&gt;fine&lt;/em&gt; idea, unless the IE Team takes the unlikely step of following Anne van Kesteren&#039;s &lt;a href=&quot;http://annevankesteren.nl/archives/2004/06/standard-compliant-ie&quot;&gt;clever suggestion&lt;/a&gt;.

Anne&#039;s suggestion seems unlikely, but it&#039;s the only &lt;em&gt;plausible&lt;/em&gt; route to &lt;em&gt;ever&lt;/em&gt; bringing true Standards support to IE. Everybody &lt;em&gt;else&lt;/em&gt; ought to be rooting for it.</description>
		<content:encoded><![CDATA[<p>Deliberately invalidating (more importantly, rendering ill-formed) every page of your site is a <em>fine</em> idea, unless the IE Team takes the unlikely step of following Anne van Kesteren&#8217;s <a href="http://annevankesteren.nl/archives/2004/06/standard-compliant-ie">clever suggestion</a>.</p>
<p>Anne&#8217;s suggestion seems unlikely, but it&#8217;s the only <em>plausible</em> route to <em>ever</em> bringing true Standards support to IE. Everybody <em>else</em> ought to be rooting for it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

