<?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"
	>
<channel>
	<title>Comments on: Version targeting in IE 8, and an alternative path for Microsoft</title>
	<atom:link href="http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/</link>
	<description>Web development and Internet trends</description>
	<pubDate>Sat, 30 Aug 2008 00:01:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: IE 8 will use Standards Mode as the default rendering - Robert&#8217;s talk - Web development and Internet trends</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-223152</link>
		<dc:creator>IE 8 will use Standards Mode as the default rendering - Robert&#8217;s talk - Web development and Internet trends</dc:creator>
		<pubDate>Tue, 04 Mar 2008 09:29:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-223152</guid>
		<description>[...] expressed my concern in Version targeting in IE 8, and an alternative path for Microsoft and IE 8, shooting browsers and what to do, and was even willing to compromise if they delivered a [...]</description>
		<content:encoded><![CDATA[<p>[...] expressed my concern in Version targeting in <acronym title="Internet Explorer">IE</acronym> 8, and an alternative path for Microsoft and <acronym title="Internet Explorer">IE</acronym> 8, shooting browsers and what to do, and was even willing to compromise if they delivered a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IE 8, shooting browsers and what to do - Robert&#8217;s talk - Web development and Internet trends</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-218223</link>
		<dc:creator>IE 8, shooting browsers and what to do - Robert&#8217;s talk - Web development and Internet trends</dc:creator>
		<pubDate>Mon, 25 Feb 2008 14:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-218223</guid>
		<description>[...] It&#8217;s a recommended read, Jeremy&#8217;s a smart and eloquent man. I do think it&#8217;s vital that we try to convince the IE team why we definitely don&#8217;t want that. My suggested solution for Microsoft is described in Version Targeting In IE 8, And An Alternative Path For Microsoft. [...]</description>
		<content:encoded><![CDATA[<p>[...] It&#8217;s a recommended read, Jeremy&#8217;s a smart and eloquent man. I do think it&#8217;s vital that we try to convince the <acronym title="Internet Explorer">IE</acronym> team why we definitely don&#8217;t want that. My suggested solution for Microsoft is described in Version Targeting In <acronym title="Internet Explorer">IE</acronym> 8, And An Alternative Path For Microsoft. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What&#8217;s Best for Web Standards? - Beast-Blog.com</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-197416</link>
		<dc:creator>What&#8217;s Best for Web Standards? - Beast-Blog.com</dc:creator>
		<pubDate>Wed, 30 Jan 2008 21:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-197416</guid>
		<description>[...] Version targeting in IE 8, and an alternative path for Microsoft by Robert Nyman [...]</description>
		<content:encoded><![CDATA[<p>[...] Version targeting in <acronym title="Internet Explorer">IE</acronym> 8, and an alternative path for Microsoft by Robert Nyman [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IE8, Version Targeting, and the Ruckus it&#8217;s Causing - Monday By Noon</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-195355</link>
		<dc:creator>IE8, Version Targeting, and the Ruckus it&#8217;s Causing - Monday By Noon</dc:creator>
		<pubDate>Mon, 28 Jan 2008 14:03:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-195355</guid>
		<description>[...] Version Targeting In IE 8, And An Alternative Path For Microsoft by Robert Nyman [...]</description>
		<content:encoded><![CDATA[<p>[...] Version Targeting In <acronym title="Internet Explorer">IE</acronym> 8, And An Alternative Path For Microsoft by Robert Nyman [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Nyman</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193528</link>
		<dc:creator>Robert Nyman</dc:creator>
		<pubDate>Fri, 25 Jan 2008 21:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193528</guid>
		<description>Aldrik,

Well, there are a number of alternative routes they could've gone with adding something more to distinguish mode, support etc, but personally I don't t adding anything more is the way to go.</description>
		<content:encoded><![CDATA[<p>Aldrik,</p>
<p>Well, there are a number of alternative routes they could&#8217;ve gone with adding something more to distinguish mode, support etc, but personally I don&#8217;t t adding anything more is the way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aldrik</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193461</link>
		<dc:creator>Aldrik</dc:creator>
		<pubDate>Fri, 25 Jan 2008 20:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193461</guid>
		<description>I think a proprietary css property perhaps could have been a better way to trigger compatibility modes rather than a meta tag (you know separation of style from content). I agree with Gerben and think that &lt;em&gt;another&lt;/em&gt; opt-in approach can only hurt web standards. 

I also refuse to put anything in my pages that's going to course users to get a message saying they have to update their browser (and quite possibly go buy a newer version on windows), instead of seeing the site they came to view.</description>
		<content:encoded><![CDATA[<p>I think a proprietary <acronym title="Cascading Style Sheets">CSS</acronym> property perhaps could have been a better way to trigger compatibility modes rather than a meta tag (you know separation of style from content). I agree with Gerben and think that <em>another</em> opt-in approach can only hurt web standards. </p>
<p>I also refuse to put anything in my pages that&#8217;s going to course users to get a message saying they have to update their browser (and quite possibly go buy a newer version on windows), instead of seeing the site they came to view.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bram.us &#187; IE8 Mode?</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193411</link>
		<dc:creator>Bram.us &#187; IE8 Mode?</dc:creator>
		<pubDate>Fri, 25 Jan 2008 18:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-193411</guid>
		<description>[...] in the most recent ALA issue (got some time to read up?): #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12, #13 and - my favorite - #14. *phew*  Spread the [...]</description>
		<content:encoded><![CDATA[<p>[...] in the most recent ALA issue (got some time to read up?): #1, #2, #3, #4, #5, #6, #7, #8, #9, #10, #11, #12, #13 and - my favorite - #14. *phew*  Spread the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Nyman</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-192123</link>
		<dc:creator>Robert Nyman</dc:creator>
		<pubDate>Thu, 24 Jan 2008 10:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-192123</guid>
		<description>Thanks for your comments!

I think, now or later, that Microsoft will have to scrap the old, and in with the new. The bulk of IE must be becoming unbearable. Netscape came to that point, with the advent of Mozilla and Firefox, and Microsoft will too.

In my opinion, its better to do that now than later. The web evolves, and products can't be backwards compatible forever, especially not with invalid code to begin with.

Here's to hoping that Microsoft will care about web professionals interested in developing good web sites, instead of those that made a non-successful attempt five years ago.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments!</p>
<p>I think, now or later, that Microsoft will have to scrap the old, and in with the new. The bulk of <acronym title="Internet Explorer">IE</acronym> must be becoming unbearable. Netscape came to that point, with the advent of Mozilla and Firefox, and Microsoft will too.</p>
<p>In my opinion, its better to do that now than later. The web evolves, and products can&#8217;t be backwards compatible forever, especially not with invalid code to begin with.</p>
<p>Here&#8217;s to hoping that Microsoft will care about web professionals interested in developing good web sites, instead of those that made a non-successful attempt five years ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 48-Hour Days &#187; Blog Archive &#187; Give Microsoft a Pat on the Back</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191997</link>
		<dc:creator>48-Hour Days &#187; Blog Archive &#187; Give Microsoft a Pat on the Back</dc:creator>
		<pubDate>Thu, 24 Jan 2008 04:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191997</guid>
		<description>[...] Version targeting in IE 8, and an alternative path for Microsoft [...]</description>
		<content:encoded><![CDATA[<p>[...] Version targeting in <acronym title="Internet Explorer">IE</acronym> 8, and an alternative path for Microsoft [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Blog Archive &#187; The Version Targeting In IE8 Proposal - StevenClark.com.au</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191862</link>
		<dc:creator>&#187; Blog Archive &#187; The Version Targeting In IE8 Proposal - StevenClark.com.au</dc:creator>
		<pubDate>Wed, 23 Jan 2008 23:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191862</guid>
		<description>[...] Robert Nyman&#8217;s Version targeting in IE 8, and an alternative path for Microsoft [...]</description>
		<content:encoded><![CDATA[<p>[...] Robert Nyman&#8217;s Version targeting in <acronym title="Internet Explorer">IE</acronym> 8, and an alternative path for Microsoft [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Blog Archive &#187; Are You Pro Version Targeting in IE8? - StevenClark.com.au</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191860</link>
		<dc:creator>&#187; Blog Archive &#187; Are You Pro Version Targeting in IE8? - StevenClark.com.au</dc:creator>
		<pubDate>Wed, 23 Jan 2008 23:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191860</guid>
		<description>[...] Robert Nyman&#8217;s Version targeting in IE 8, and an alternative path for Microsoft [...]</description>
		<content:encoded><![CDATA[<p>[...] Robert Nyman&#8217;s Version targeting in <acronym title="Internet Explorer">IE</acronym> 8, and an alternative path for Microsoft [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Clark</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191828</link>
		<dc:creator>Steven Clark</dc:creator>
		<pubDate>Wed, 23 Jan 2008 21:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191828</guid>
		<description>My gut instinct is this isn't the way to go... I've rewritten this comment every which way and the problem is complex. I like the separate IE install suggestion but wonder if their issue with that isn't the tight integration with their OS? Also, with multiple installs, someone like Amazon with ecommerce customers will lose business if there was a requirement for multiple versions - most customers barely use email correctly and couldn't install multiple versions of a word document they wrote yesterday lol... but I think multiple versions side by side is something they should do.

Eric Meyer's article on ALA was very balanced but I'm left with prickles of caution from his closing paragraphs - bloatware might be an issue if IE7 will be a part of IE14 for example. And the inevitable new bugs introduced with iterations of software, where's the guarantee the legacy support for IE7 won't be broken somewhere down the track so we end up with IE7 original rendering of some features and IE14 rendering of IE7... bugs are inevitable in this.

It seems like a trend of the last year to dumb down to meet the market for web standards. HTML 5 to meet the Flickr case study on alternate text, for example. This time to placate IE. The business case makes sense on the surface but we have to remind ourselves that just because WaSP sanctions something doesn't make it the holy grail of web standards... there was another company that took a big hit from rebuilding their browser from the ground up by the way...

When it comes down to it we're really talking about the reality that IE owns the show right?

All that being said I do appreciate the other side of the coin. If we could rejumble a bunch of stuff today that gave us a working across the board web development industry tomorrow (IE that is not broken for us) then how much are we willing to pay? Because at the end of the day IE coming into line will eventually cost us one way or another. Micro-costs alone for fixing IE bugs on each project on a worldwide basis must be billions for the industry...

Sorry for the long babble... at this stage I only have my gut feeling of "Danger Will Robinson, aliens approaching!"</description>
		<content:encoded><![CDATA[<p>My gut instinct is this isn&#8217;t the way to go&#8230; I&#8217;ve rewritten this comment every which way and the problem is complex. I like the separate <acronym title="Internet Explorer">IE</acronym> install suggestion but wonder if their issue with that isn&#8217;t the tight integration with their OS? Also, with multiple installs, someone like Amazon with ecommerce customers will lose business if there was a requirement for multiple versions - most customers barely use email correctly and couldn&#8217;t install multiple versions of a word document they wrote yesterday lol&#8230; but I think multiple versions side by side is something they should do.</p>
<p>Eric Meyer&#8217;s article on ALA was very balanced but I&#8217;m left with prickles of caution from his closing paragraphs - bloatware might be an issue if IE7 will be a part of IE14 for example. And the inevitable new bugs introduced with iterations of software, where&#8217;s the guarantee the legacy support for IE7 won&#8217;t be broken somewhere down the track so we end up with IE7 original rendering of some features and IE14 rendering of IE7&#8230; bugs are inevitable in this.</p>
<p>It seems like a trend of the last year to dumb down to meet the market for web standards. <acronym title="HyperText Markup Language">HTML</acronym> 5 to meet the Flickr case study on alternate text, for example. This time to placate <acronym title="Internet Explorer">IE</acronym>. The business case makes sense on the surface but we have to remind ourselves that just because WaSP sanctions something doesn&#8217;t make it the holy grail of web standards&#8230; there was another company that took a big hit from rebuilding their browser from the ground up by the way&#8230;</p>
<p>When it comes down to it we&#8217;re really talking about the reality that <acronym title="Internet Explorer">IE</acronym> owns the show right?</p>
<p>All that being said I do appreciate the other side of the coin. If we could rejumble a bunch of stuff today that gave us a working across the board web development industry tomorrow (<acronym title="Internet Explorer">IE</acronym> that is not broken for us) then how much are we willing to pay? Because at the end of the day <acronym title="Internet Explorer">IE</acronym> coming into line will eventually cost us one way or another. Micro-costs alone for fixing <acronym title="Internet Explorer">IE</acronym> bugs on each project on a worldwide basis must be billions for the industry&#8230;</p>
<p>Sorry for the long babble&#8230; at this stage I only have my gut feeling of &#8220;Danger Will Robinson, aliens approaching!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerben</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191703</link>
		<dc:creator>Gerben</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:59:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191703</guid>
		<description>I think the version targeting is okay, but to get rid of the crappy IE rendering heritage they should make it opt-out instead of opt-in. 
Developers already had to fix sites to make them work in IE7. When IE8 comes out (lazy) developers only have to add a single meta IE=7 tag and they are done. I think this is a small sacrifice to make and it will make IE8, by default, behave like all the other standards compliant browsers.

Also people new to the web, and not knowing about the meta element, won't have to bang their heads to their desks because IE isn't doing what all other browser are doing.</description>
		<content:encoded><![CDATA[<p>I think the version targeting is okay, but to get rid of the crappy <acronym title="Internet Explorer">IE</acronym> rendering heritage they should make it opt-out instead of opt-in.<br />
Developers already had to fix sites to make them work in IE7. When IE8 comes out (lazy) developers only have to add a single meta <acronym title="Internet Explorer">IE</acronym>=7 tag and they are done. I think this is a small sacrifice to make and it will make IE8, by default, behave like all the other standards compliant browsers.</p>
<p>Also people new to the web, and not knowing about the meta element, won&#8217;t have to bang their heads to their desks because <acronym title="Internet Explorer">IE</acronym> isn&#8217;t doing what all other browser are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobertDM</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191682</link>
		<dc:creator>RobertDM</dc:creator>
		<pubDate>Wed, 23 Jan 2008 16:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191682</guid>
		<description>My biggest concern is that it will fuel the non-believers of web standards to stick with their bad habbits. They will be confirmed in their belief that they don't need standards, just use version targeting and things are just fine. 
I'm also afraid this will be convienient for Microsoft: if they can get everyone to use version targeting, switching to newer browserversions will not reveal code deficiënties and therefore lessen the need for fixes. I don't really follow Eric Meyer's view on this on ALA where he is confident it will lead to quicker bugfixing. (but then again who am I ;-) )</description>
		<content:encoded><![CDATA[<p>My biggest concern is that it will fuel the non-believers of web standards to stick with their bad habbits. They will be confirmed in their belief that they don&#8217;t need standards, just use version targeting and things are just fine.<br />
I&#8217;m also afraid this will be convienient for Microsoft: if they can get everyone to use version targeting, switching to newer browserversions will not reveal code deficiënties and therefore lessen the need for fixes. I don&#8217;t really follow Eric Meyer&#8217;s view on this on ALA where he is confident it will lead to quicker bugfixing. (but then again who am I <img src='http://www.robertnyman.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191665</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 23 Jan 2008 15:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191665</guid>
		<description>I was soooo upset when I red about it at ALA. IE8 is a piece of crap, it doesnt work as napoleon dynamite would say. +1 for multiple installs of IE   though i really see their problem, building an rendering motor for the web cant be the easiest thing to do... while on that subject check this out: http://ejohn.org/blog/sub-pixel-problems-in-css/</description>
		<content:encoded><![CDATA[<p>I was soooo upset when I red about it at ALA. IE8 is a piece of crap, it doesnt work as napoleon dynamite would say. +1 for multiple installs of <acronym title="Internet Explorer">IE</acronym>   though i really see their problem, building an rendering motor for the web cant be the easiest thing to do&#8230; while on that subject check this out: <a href="http://ejohn.org/blog/sub-pixel-problems-in-css/" rel="nofollow">http://ejohn.org/blog/sub-pixel-problems-in-<acronym title="Cascading Style Sheets">CSS</acronym>/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lim Chee Aun</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191622</link>
		<dc:creator>Lim Chee Aun</dc:creator>
		<pubDate>Wed, 23 Jan 2008 14:14:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191622</guid>
		<description>I agree as well that multiple installs of IE is essential. It may not be useful for users/visitors, but it will be for 'concerned' web developers and webmasters. Even though the process of 'upgrading' IE6-optimized or quirks-mode-optimized web pages to standard-compliant ones may be 'difficult' now, but after some time, once this is over, it'll be easy when *all* browsers have the same high level implementation of standards.</description>
		<content:encoded><![CDATA[<p>I agree as well that multiple installs of <acronym title="Internet Explorer">IE</acronym> is essential. It may not be useful for users/visitors, but it will be for &#8216;concerned&#8217; web developers and webmasters. Even though the process of &#8216;upgrading&#8217; IE6-optimized or quirks-mode-optimized web pages to standard-compliant ones may be &#8216;difficult&#8217; now, but after some time, once this is over, it&#8217;ll be easy when *all* browsers have the same high level implementation of standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191617</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Wed, 23 Jan 2008 14:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191617</guid>
		<description>Great! Another rendering mode for IE...
&lt;blockquote cite="http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/"&gt;
IE 8 will behave exactly like IE 7, unless you specifically tell it to behave better&lt;/blockquote&gt;
Well, I hope that it will at least be the exact same rendering mode if you don't specify this meta tag.
Moreover, why not specify IE8 that you want to use the IE7 rendering mode by specifying the meta tag, and without it activate this "super new now really standard mode", thus making the new mode the default one?

Your proposition to be able to have multiple versions of IE side by side (officially supported by MS) would a major step in the right direction. I am not sure we will see it anytime soon...</description>
		<content:encoded><![CDATA[<p>Great! Another rendering mode for <acronym title="Internet Explorer">IE</acronym>&#8230;</p>
<blockquote cite="http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/"><p>
<acronym title="Internet Explorer">IE</acronym> 8 will behave exactly like <acronym title="Internet Explorer">IE</acronym> 7, unless you specifically tell it to behave better</p></blockquote>
<p>Well, I hope that it will at least be the exact same rendering mode if you don&#8217;t specify this meta tag.<br />
Moreover, why not specify IE8 that you want to use the IE7 rendering mode by specifying the meta tag, and without it activate this &#8220;super new now really standard mode&#8221;, thus making the new mode the default one?</p>
<p>Your proposition to be able to have multiple versions of <acronym title="Internet Explorer">IE</acronym> side by side (officially supported by <acronym title="Microsoft">MS</acronym>) would a major step in the right direction. I am not sure we will see it anytime soon&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191604</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Wed, 23 Jan 2008 13:56:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/2008/01/23/version-targeting-in-ie-8-and-an-alternative-path-for-microsoft/#comment-191604</guid>
		<description>Interesting ideas Robert, I particularly like the one about allowing multiple installs of IE. It would help with development and rolling software out to those companies with legacy systems that require ancient versions of IE to work.

However, while mutiple installs may be a sufficient system for companies and legacy systems, this cannot be a good option for users. If you were surfing the web and a site gave you a "Please view this page in IE7" notice and you were using IE8, or 9, or 20, how long would you stick around for?

I think the perspective actually has to be from a user in terms of this change. When IE7 "broke the web" there were developers panicking, but there were far more confused users. This is Microsoft's fault for not updating browsers and for getting standards wrong (I don't believe that other browsers should adopt this version targeting), so the emphasis is now on them to provide a solution that won't break anything for users in such a big way again. I think a lean, standards only IE8 would do that. Not forgetting that many sites out there don't follow standards and work based on browser quirks in the standards modes. In an ideal world, all sites would be coded to the standards and bringing out only one, standards compliant browser would fix the web.

&lt;a href="http://www.unintentionallyblank.co.uk/2008/01/23/version-targeting-for-ie8-developer-wars-my-thoughts/" rel="nofollow"&gt;I have more thoughts on my blog&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Interesting ideas Robert, I particularly like the one about allowing multiple installs of <acronym title="Internet Explorer">IE</acronym>. It would help with development and rolling software out to those companies with legacy systems that require ancient versions of <acronym title="Internet Explorer">IE</acronym> to work.</p>
<p>However, while mutiple installs may be a sufficient system for companies and legacy systems, this cannot be a good option for users. If you were surfing the web and a site gave you a &#8220;Please view this page in IE7&#8243; notice and you were using IE8, or 9, or 20, how long would you stick around for?</p>
<p>I think the perspective actually has to be from a user in terms of this change. When IE7 &#8220;broke the web&#8221; there were developers panicking, but there were far more confused users. This is Microsoft&#8217;s fault for not updating browsers and for getting standards wrong (I don&#8217;t believe that other browsers should adopt this version targeting), so the emphasis is now on them to provide a solution that won&#8217;t break anything for users in such a big way again. I think a lean, standards only IE8 would do that. Not forgetting that many sites out there don&#8217;t follow standards and work based on browser quirks in the standards modes. In an ideal world, all sites would be coded to the standards and bringing out only one, standards compliant browser would fix the web.</p>
<p><a href="http://www.unintentionallyblank.co.uk/2008/01/23/version-targeting-for-ie8-developer-wars-my-thoughts/" rel="nofollow">I have more thoughts on my blog</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
