<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IE 8 Beta 2 Impressions</title>
	<atom:link href="http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/feed/" rel="self" type="application/rss+xml" />
	<link>http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/</link>
	<description>Long lead times need long forward planning</description>
	<lastBuildDate>Tue, 23 Sep 2008 07:22:09 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: cquirke</title>
		<link>http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/#comment-95</link>
		<dc:creator>cquirke</dc:creator>
		<pubDate>Tue, 23 Sep 2008 07:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/#comment-95</guid>
		<description>At some point, we should see regular builds, for testers to assess whether bugs are fixed and ensure new bugs don&#039;t arise.  However, these builds will probably not be waved around as publically as IE8b2 and what I expect to be a later and more widespread acceptability-tester.  

That&#039;s not a matter of &quot;secrecy&quot;, just that the resources needed to publicize and distribute a public beta wouldn&#039;t be well-spent by repeating the process for each week&#039;s new build.  The folks who will actually test such things will be hooked into Connect, and from there, it should be easy to find and pull the new beta builds.

The other option is to what MS already did with IE8b2 over IE8b1; deliver the new build as an automatic update.

Firefox is nice because it&#039;s self-contained and small, so patching just becomes a matter of replacing the whole thing.  However, this nearly always breaks extensions, leading to prompts to &quot;look for new versions&quot; that could be used to keep malware current and ahead of av detection.  Personally, I hate plugins and extensions, so I&#039;m happy to slough them off    :-)

IEb2&#039;s still a bit wobbly, and in ways that are different to IEb1 (i.e. some old bugs fixed, some new bug patterns added) - so we definitely need some more builds before RC or RTM status.</description>
		<content:encoded><![CDATA[<p>At some point, we should see regular builds, for testers to assess whether bugs are fixed and ensure new bugs don&#8217;t arise.  However, these builds will probably not be waved around as publically as IE8b2 and what I expect to be a later and more widespread acceptability-tester.  </p>
<p>That&#8217;s not a matter of &#8220;secrecy&#8221;, just that the resources needed to publicize and distribute a public beta wouldn&#8217;t be well-spent by repeating the process for each week&#8217;s new build.  The folks who will actually test such things will be hooked into Connect, and from there, it should be easy to find and pull the new beta builds.</p>
<p>The other option is to what MS already did with IE8b2 over IE8b1; deliver the new build as an automatic update.</p>
<p>Firefox is nice because it&#8217;s self-contained and small, so patching just becomes a matter of replacing the whole thing.  However, this nearly always breaks extensions, leading to prompts to &#8220;look for new versions&#8221; that could be used to keep malware current and ahead of av detection.  Personally, I hate plugins and extensions, so I&#8217;m happy to slough them off    :-)</p>
<p>IEb2&#8217;s still a bit wobbly, and in ways that are different to IEb1 (i.e. some old bugs fixed, some new bug patterns added) &#8211; so we definitely need some more builds before RC or RTM status.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan W.</title>
		<link>http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/#comment-94</link>
		<dc:creator>Dan W.</dc:creator>
		<pubDate>Tue, 23 Sep 2008 03:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://cquirke.wordpress.com/2008/09/11/ie-8-beta-2-impressions/#comment-94</guid>
		<description>I agree Chris and I do hope that there are more Internet Explorer 8 betas as well and I was kind of forced into using Internet Explorer 8 after I wanted to downgrade to Internet Explorer 6 and ran into *.dll h_ll.  Anyway, I am now using Internet Explorer 8 beta 2 and do enjoy it.  I hope Microsoft will at the bare minimum have a 3rd beta of Internet Explorer and hopefully even more because the more fully the web browser is tested the better it will be in the end.  I am still saddened that a user must use Mozilla Firefox to allow for 256 bit AES (Advanced Encryption Standard) or use Windows Vista which allows for 256 bit AES cipher strength.  I have asked Microsoft for this level of security in Windows XP Professional but was turned down flat and so I know that Mozilla Firefox 2.x will remain my browser of choice for now.  Sure, Mozilla Firefox 3.x has better security but still lacks some compatibility with extensions so there is no rush for me.  I am not usually an early adopter of new technology but I certainly enjoy being a tester of new software that has the chance to be used by millions or even billions of users around the world.</description>
		<content:encoded><![CDATA[<p>I agree Chris and I do hope that there are more Internet Explorer 8 betas as well and I was kind of forced into using Internet Explorer 8 after I wanted to downgrade to Internet Explorer 6 and ran into *.dll h_ll.  Anyway, I am now using Internet Explorer 8 beta 2 and do enjoy it.  I hope Microsoft will at the bare minimum have a 3rd beta of Internet Explorer and hopefully even more because the more fully the web browser is tested the better it will be in the end.  I am still saddened that a user must use Mozilla Firefox to allow for 256 bit AES (Advanced Encryption Standard) or use Windows Vista which allows for 256 bit AES cipher strength.  I have asked Microsoft for this level of security in Windows XP Professional but was turned down flat and so I know that Mozilla Firefox 2.x will remain my browser of choice for now.  Sure, Mozilla Firefox 3.x has better security but still lacks some compatibility with extensions so there is no rush for me.  I am not usually an early adopter of new technology but I certainly enjoy being a tester of new software that has the chance to be used by millions or even billions of users around the world.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
