<?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: Chris Wilson keynote at TAE</title>
	<atom:link href="http://ajaxian.com/archives/chris-wilson-keynote-at-tae/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Frank Thuerigen</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253248</link>
		<dc:creator>Frank Thuerigen</dc:creator>
		<pubDate>Fri, 27 Jul 2007 16:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253248</guid>
		<description>It doesnÂ´t look like Microsoft will redesign IE8 to be standards compliant. I would just take it as it is and hope we donÂ´t get another non-standards non-IE6 non-IE7 next version of the explorer (the third way). I kind of made peace with the situation - because there is no way I could change whatever Microsoft is up to. From a business point of view: cross browser testing will never be a part of a fixed price project here.</description>
		<content:encoded><![CDATA[<p>It doesnÂ´t look like Microsoft will redesign IE8 to be standards compliant. I would just take it as it is and hope we donÂ´t get another non-standards non-IE6 non-IE7 next version of the explorer (the third way). I kind of made peace with the situation &#8211; because there is no way I could change whatever Microsoft is up to. From a business point of view: cross browser testing will never be a part of a fixed price project here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ktrott</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253247</link>
		<dc:creator>ktrott</dc:creator>
		<pubDate>Fri, 27 Jul 2007 15:56:05 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253247</guid>
		<description>I think that Microsoft is overly concerned about not breaking the Web to the point where they become enablers of abuse. The idea that a page could declare a standards mode DOCTYPE but IE would say &quot;well you said you wanted standards mode but we don&#039;t really think that&#039;s what you meant, so if you really want standards mode you&#039;ll need to also declare something in a conditional comment or meta tag&quot; is absolutely ridiculous. They are concerned that currently lots of people are using standards mode not realizing what they are getting/doing and there&#039;s a lot of existing pages built this way. Well IE, if you hadn&#039;t done it wrong in the first place, there probably wouldn&#039;t be this problem. But don&#039;t hold the development of the Web back just because a set of people don&#039;t know what they&#039;re doing. Don&#039;t diverge again from all the other browsers and standard just to enable people to use things incorrectly. What about me? I really do want standards mode and if I specify the right DOCTYPE I should get it. Period. I shouldn&#039;t have to also use yet another IE specific way of doing things.</description>
		<content:encoded><![CDATA[<p>I think that Microsoft is overly concerned about not breaking the Web to the point where they become enablers of abuse. The idea that a page could declare a standards mode DOCTYPE but IE would say &#8220;well you said you wanted standards mode but we don&#8217;t really think that&#8217;s what you meant, so if you really want standards mode you&#8217;ll need to also declare something in a conditional comment or meta tag&#8221; is absolutely ridiculous. They are concerned that currently lots of people are using standards mode not realizing what they are getting/doing and there&#8217;s a lot of existing pages built this way. Well IE, if you hadn&#8217;t done it wrong in the first place, there probably wouldn&#8217;t be this problem. But don&#8217;t hold the development of the Web back just because a set of people don&#8217;t know what they&#8217;re doing. Don&#8217;t diverge again from all the other browsers and standard just to enable people to use things incorrectly. What about me? I really do want standards mode and if I specify the right DOCTYPE I should get it. Period. I shouldn&#8217;t have to also use yet another IE specific way of doing things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Whoops I annoyed you</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253245</link>
		<dc:creator>Whoops I annoyed you</dc:creator>
		<pubDate>Fri, 27 Jul 2007 15:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253245</guid>
		<description>Here&#039;s a though MS, don&#039;t move the refresh button to a tiny button the other side of the URL location.  I can&#039;t tell you how many times a day I fumble around with that.  Start watching yourself and you&#039;ll have a very clear and continuous non-CSS / JS hack annoyance with IE.  Whatever usability wonk told them this was a good idea esp. with all the other browsers doing it the old way out to be run out of the industry.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a though MS, don&#8217;t move the refresh button to a tiny button the other side of the URL location.  I can&#8217;t tell you how many times a day I fumble around with that.  Start watching yourself and you&#8217;ll have a very clear and continuous non-CSS / JS hack annoyance with IE.  Whatever usability wonk told them this was a good idea esp. with all the other browsers doing it the old way out to be run out of the industry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: todd</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253230</link>
		<dc:creator>todd</dc:creator>
		<pubDate>Fri, 27 Jul 2007 09:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253230</guid>
		<description>What I loved about the keynote:

1. Chris stated that because of IE7, 50% of the top 200 websites are now running in &#039;standards&#039; mode and not &#039;quirks&#039; mode......but in reality, the reason they&#039;re running in &#039;standards&#039; mode is because they know they have to code for Firefox and other standards compliant browsers.  So they&#039;ve gone ahead and coded it the right way, and then hacked the code to work in IE.

2. He more or less said that IE7 is not standards compliant because M$ doesn&#039;t want to &#039;break the web&#039;.  He used some mundane examples of how his mothers bank website wouldn&#039;t work if they made major changes to IE7.  But what he failed to mention is that ANY respectable financial institution has allready coded their site for FF, so she has the option to use a browser that works, while IE7 gets their asses in gear.

3. What Chris failed to realize is that every waking moment that they ship a sub par, non-standards compliant product, that means more and more websites get created using the hacks that he says will &#039;break the web&#039; if they get removed.  So all of his answers for why IE is non compliant pose paradoxes.  

One solution that I see to this, is to start fresh with IE8.  Fix whatever issues there are in IE7, then mothball the project.  Allow IE8 to be a separate and non mandatory install that will not overwrite IE7.  This way, you start with a new code base that can be made standards compliant and not use cloogy proprietary technology.  It would also allow for all current websites to still work, thus not &#039;breaking the web&#039; but then give them the ability and time to remove any hacks that might exist and create their sites they way they should be created.

M$ doesn&#039;t charge for their browser, so why develop it in a manner that lends itself to competition?  Theres no need for market share in a browser.  I may be wrong on that, and i challenge anyone to show me the fault in that statement, because i would love to know.  But if they do in fact want to keep their &quot;market share&quot; they need to immediately tuen 180 degrees and begin listening to the people.  If that doesnt not happen, the effect will be that FF takes over as the market share leader, and they wont have to look back.  As long as they would stay compliant, there would be nothing that IE could do to regain the ground.</description>
		<content:encoded><![CDATA[<p>What I loved about the keynote:</p>
<p>1. Chris stated that because of IE7, 50% of the top 200 websites are now running in &#8216;standards&#8217; mode and not &#8216;quirks&#8217; mode&#8230;&#8230;but in reality, the reason they&#8217;re running in &#8216;standards&#8217; mode is because they know they have to code for Firefox and other standards compliant browsers.  So they&#8217;ve gone ahead and coded it the right way, and then hacked the code to work in IE.</p>
<p>2. He more or less said that IE7 is not standards compliant because M$ doesn&#8217;t want to &#8216;break the web&#8217;.  He used some mundane examples of how his mothers bank website wouldn&#8217;t work if they made major changes to IE7.  But what he failed to mention is that ANY respectable financial institution has allready coded their site for FF, so she has the option to use a browser that works, while IE7 gets their asses in gear.</p>
<p>3. What Chris failed to realize is that every waking moment that they ship a sub par, non-standards compliant product, that means more and more websites get created using the hacks that he says will &#8216;break the web&#8217; if they get removed.  So all of his answers for why IE is non compliant pose paradoxes.  </p>
<p>One solution that I see to this, is to start fresh with IE8.  Fix whatever issues there are in IE7, then mothball the project.  Allow IE8 to be a separate and non mandatory install that will not overwrite IE7.  This way, you start with a new code base that can be made standards compliant and not use cloogy proprietary technology.  It would also allow for all current websites to still work, thus not &#8216;breaking the web&#8217; but then give them the ability and time to remove any hacks that might exist and create their sites they way they should be created.</p>
<p>M$ doesn&#8217;t charge for their browser, so why develop it in a manner that lends itself to competition?  Theres no need for market share in a browser.  I may be wrong on that, and i challenge anyone to show me the fault in that statement, because i would love to know.  But if they do in fact want to keep their &#8220;market share&#8221; they need to immediately tuen 180 degrees and begin listening to the people.  If that doesnt not happen, the effect will be that FF takes over as the market share leader, and they wont have to look back.  As long as they would stay compliant, there would be nothing that IE could do to regain the ground.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Ritchie</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253228</link>
		<dc:creator>Mike Ritchie</dc:creator>
		<pubDate>Fri, 27 Jul 2007 08:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253228</guid>
		<description>All I want is for IE to give me the *actual* line number on the *actual* file that my javascript error is coming from.  &quot;Line 20: Object does not support that method&quot; leaves me no closer to understanding the source of the error than I was before I double-click on the error prompt.</description>
		<content:encoded><![CDATA[<p>All I want is for IE to give me the *actual* line number on the *actual* file that my javascript error is coming from.  &#8220;Line 20: Object does not support that method&#8221; leaves me no closer to understanding the source of the error than I was before I double-click on the error prompt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Cooijmans</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253227</link>
		<dc:creator>Tim Cooijmans</dc:creator>
		<pubDate>Fri, 27 Jul 2007 08:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253227</guid>
		<description>So where do I get Visual Web Developer Expres?  The download center doesn&#039;t list it.</description>
		<content:encoded><![CDATA[<p>So where do I get Visual Web Developer Expres?  The download center doesn&#8217;t list it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael van Ouwerkerk</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253226</link>
		<dc:creator>Michael van Ouwerkerk</dc:creator>
		<pubDate>Fri, 27 Jul 2007 07:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253226</guid>
		<description>If we are to move forward and start running IE in standards compliant mode, I have one simple requirement and it&#039;s a single CSS property: support box-sizing.

http://www.w3.org/TR/css3-ui/#box-sizing

In setting up the Backbase widget library my experience has been that not having support for this property can easily lead to ugly hacks and attempts at writing non standards compliant code, only for IE.

The content-box model specified in CSS2.1 is just not the most suitable for all situations, so a document level switch (the way IE implemented control over box sizing) is clearly insufficient and hinders adoption of the standards.</description>
		<content:encoded><![CDATA[<p>If we are to move forward and start running IE in standards compliant mode, I have one simple requirement and it&#8217;s a single CSS property: support box-sizing.</p>
<p><a href="http://www.w3.org/TR/css3-ui/#box-sizing" rel="nofollow">http://www.w3.org/TR/css3-ui/#box-sizing</a></p>
<p>In setting up the Backbase widget library my experience has been that not having support for this property can easily lead to ugly hacks and attempts at writing non standards compliant code, only for IE.</p>
<p>The content-box model specified in CSS2.1 is just not the most suitable for all situations, so a document level switch (the way IE implemented control over box sizing) is clearly insufficient and hinders adoption of the standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cdude</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253217</link>
		<dc:creator>cdude</dc:creator>
		<pubDate>Fri, 27 Jul 2007 03:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253217</guid>
		<description>The only way to move the web forward is for all web developers to unite and say no to IE hacks and work-arounds. I doubt many will adopt this so we&#039;ll keep on whining and the IE team will keep on preaching web standards.</description>
		<content:encoded><![CDATA[<p>The only way to move the web forward is for all web developers to unite and say no to IE hacks and work-arounds. I doubt many will adopt this so we&#8217;ll keep on whining and the IE team will keep on preaching web standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GMFlash</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253214</link>
		<dc:creator>GMFlash</dc:creator>
		<pubDate>Fri, 27 Jul 2007 02:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253214</guid>
		<description>I think it&#039;s funny that the Platform Architect of Internet Explorer called his keynote &quot;Moving The Web Forward&quot;.  Guess he doesn&#039;t realize that his product has been HOLDING THE WEB BACK all these years!</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s funny that the Platform Architect of Internet Explorer called his keynote &#8220;Moving The Web Forward&#8221;.  Guess he doesn&#8217;t realize that his product has been HOLDING THE WEB BACK all these years!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AndiSkater</title>
		<link>http://ajaxian.com/archives/chris-wilson-keynote-at-tae/comment-page-1#comment-253213</link>
		<dc:creator>AndiSkater</dc:creator>
		<pubDate>Fri, 27 Jul 2007 02:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2611#comment-253213</guid>
		<description>Microsoft has finally succeeded: I&#039;ll develop Flex/AIR web applications in the future. No more HTML/JS/CSS for me.

The Internet Explorer has hindered web development for years now and there seems to be is no end. There is one question I am particular interested in: How many billions of Dollars have been wasted to create workarounds for the IE?

In the company I am working for we spend a tremendous amount of time to fix IE issues...

I really hate Microsoft for making the web such an unpleased place.</description>
		<content:encoded><![CDATA[<p>Microsoft has finally succeeded: I&#8217;ll develop Flex/AIR web applications in the future. No more HTML/JS/CSS for me.</p>
<p>The Internet Explorer has hindered web development for years now and there seems to be is no end. There is one question I am particular interested in: How many billions of Dollars have been wasted to create workarounds for the IE?</p>
<p>In the company I am working for we spend a tremendous amount of time to fix IE issues&#8230;</p>
<p>I really hate Microsoft for making the web such an unpleased place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

