<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Browser Wars: Network Managers Flee IE</title>
	<link>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/</link>
	<description>Spam, Security, Privacy, Spyware, Phishing &#038; Viruses from the Front Lines.</description>
	<pubDate>Sun, 20 Jul 2008 00:55:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Tony Ackerman (former MS build lead)</title>
		<link>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-304</link>
		<pubDate>Thu, 16 Feb 2006 22:06:36 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-304</guid>
					<description>Several problems exist at Redmond wrt to IE (and more than several other components for that matter).  Part of it is coding mindset, part of it management.  &lt;br&gt; &lt;br&gt; During the production of XP, we trapped a nasty access violation dead to rights in the IE code.  We handed the bug to the dev team in IE and they found the code error right away, told us that it had been there for quite some time and that it was a good catch.  Incredibly, they were NOT allowed to check in the fix for the bug because their management denied approval of the fix because WE (the server build lab) were unable to reliably reproduce the AV.  That was the reason why it was so nasty, it was hard to get the timing right and so it was hard to catch!  But there is was, staring right out of the code!  Amazing decision!  Fought the good fight in war room and failed.   Not to be out done, one of the developers in the server team took it upon himself to fix the damn thing anyway and check it in through my lab.  We both caught hell for that, him for mucking around in someone else's code and me for taking it into the build.&lt;br&gt; &lt;br&gt; I'm no rocket scientist, but difference in mindset between the UI teams and the base and server teams was immense.  Rather than fix the bugs, the management mindset for the IE team at the time seemed to be to cover them up with exception handlers.  I didn't fault the IE developer team, there are/were some really good, talented people in that group.  Really though, if you aren't allowed to fix the bugs, then what is the point of caring?&lt;br&gt; &lt;br&gt; I'm glad I'm not there anymore.  As someone once said, it feels so good when you stop pounding your head against concrete because quits hurting so bad.</description>
		<content:encoded><![CDATA[<p>Several problems exist at Redmond wrt to IE (and more than several other components for that matter).  Part of it is coding mindset, part of it management.  </p>
<p> During the production of XP, we trapped a nasty access violation dead to rights in the IE code.  We handed the bug to the dev team in IE and they found the code error right away, told us that it had been there for quite some time and that it was a good catch.  Incredibly, they were NOT allowed to check in the fix for the bug because their management denied approval of the fix because WE (the server build lab) were unable to reliably reproduce the AV.  That was the reason why it was so nasty, it was hard to get the timing right and so it was hard to catch!  But there is was, staring right out of the code!  Amazing decision!  Fought the good fight in war room and failed.   Not to be out done, one of the developers in the server team took it upon himself to fix the damn thing anyway and check it in through my lab.  We both caught hell for that, him for mucking around in someone else&#8217;s code and me for taking it into the build.</p>
<p> I&#8217;m no rocket scientist, but difference in mindset between the UI teams and the base and server teams was immense.  Rather than fix the bugs, the management mindset for the IE team at the time seemed to be to cover them up with exception handlers.  I didn&#8217;t fault the IE developer team, there are/were some really good, talented people in that group.  Really though, if you aren&#8217;t allowed to fix the bugs, then what is the point of caring?</p>
<p> I&#8217;m glad I&#8217;m not there anymore.  As someone once said, it feels so good when you stop pounding your head against concrete because quits hurting so bad.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: warp</title>
		<link>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-303</link>
		<pubDate>Sun, 01 Jan 2006 16:56:54 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-303</guid>
					<description>Reply to Jason F:&lt;br&gt; Have you tried the Mozilla Suite (or better SeaMonkey) Zip builds yet?&lt;br&gt; (http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/)&lt;br&gt; Unzip and run, no installation needed :p</description>
		<content:encoded><![CDATA[<p>Reply to Jason F:<br /> Have you tried the Mozilla Suite (or better SeaMonkey) Zip builds yet?<br /> (http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/)<br /> Unzip and run, no installation needed :p
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jason F</title>
		<link>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-302</link>
		<pubDate>Fri, 30 Dec 2005 13:09:37 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-302</guid>
					<description>I just wanted to comment that the recent article showing the amount of traffic through your site is actually highly innacurate, in that your IE percentage is much higher than it actually should be. The reason why is that one of my jobs is within tech support under &lt;Company Name Withheld&gt;. Our site has a strict IE only policy, and our work computers are completely locked down to prevent any unathorized programs from being installed... which includes browsers like FireFox. So while I use FireFox and Opera at home and at my other jobs, I am unable to use FireFox at &lt;Company Name Withheld&gt;, thus in my view, contributing to the perception that IE has a higher traffic volume than it actually does have. And I feel sure that I am not the only reader who is forced to use IE by incompetent IT departments (hello, I work in Tech Support and I sure as hell ain't telling our clients to use IE).</description>
		<content:encoded><![CDATA[<p>I just wanted to comment that the recent article showing the amount of traffic through your site is actually highly innacurate, in that your IE percentage is much higher than it actually should be. The reason why is that one of my jobs is within tech support under <Company Name Withheld>. Our site has a strict IE only policy, and our work computers are completely locked down to prevent any unathorized programs from being installed&#8230; which includes browsers like FireFox. So while I use FireFox and Opera at home and at my other jobs, I am unable to use FireFox at <Company Name Withheld>, thus in my view, contributing to the perception that IE has a higher traffic volume than it actually does have. And I feel sure that I am not the only reader who is forced to use IE by incompetent IT departments (hello, I work in Tech Support and I sure as hell ain&#8217;t telling our clients to use IE).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Blder</title>
		<link>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-301</link>
		<pubDate>Tue, 27 Dec 2005 13:52:45 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/01/03/email_aacegjidgg_h/#comment-301</guid>
					<description>I've recently migrated my users to Firefox. It's not without its problems. For instance, it's a pain to upgrade community-created extensions when a new version of the browser is released. A lot of stuff just stops working. Overall, though, we're happy. Tabbed browsing is great, and we don't see the "blue screens of death" that we ran into so often with IE.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve recently migrated my users to Firefox. It&#8217;s not without its problems. For instance, it&#8217;s a pain to upgrade community-created extensions when a new version of the browser is released. A lot of stuff just stops working. Overall, though, we&#8217;re happy. Tabbed browsing is great, and we don&#8217;t see the &#8220;blue screens of death&#8221; that we ran into so often with IE.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
