<?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: Bad dog, IE6. Bad dog!</title>
	<atom:link href="http://it.gen.nz/2008/09/13/bad-dog-ie6-bad-dog/feed/" rel="self" type="application/rss+xml" />
	<link>http://it.gen.nz/2008/09/13/bad-dog-ie6-bad-dog/</link>
	<description>Writings on technology and society from Wellington, New Zealand</description>
	<lastBuildDate>Wed, 02 May 2012 08:16:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lawrence D'Oliveiro</title>
		<link>http://it.gen.nz/2008/09/13/bad-dog-ie6-bad-dog/comment-page-1/#comment-913</link>
		<dc:creator>Lawrence D'Oliveiro</dc:creator>
		<pubDate>Wed, 17 Sep 2008 00:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=159#comment-913</guid>
		<description>I remember my first non-trivial exercise in dynamic HTML, doing a photo-cropping function for a client&#039;s web site. After one day, I got the code working fine in both Firefox and Konqueror (apart from the latter&#039;s lack of support of transparency). I then had to spend another day (50% of the development time) putting in deliberately WRONG numbers just to get things looking right in IE6.

My verdict is, it&#039;s not worth supporting any more. Those organizations that prevent their users from running any other browser probably also restrict the kinds of sites they&#039;re allowed to visit any way, so I wouldn&#039;t worry about it.</description>
		<content:encoded><![CDATA[<p>I remember my first non-trivial exercise in dynamic HTML, doing a photo-cropping function for a client&#8217;s web site. After one day, I got the code working fine in both Firefox and Konqueror (apart from the latter&#8217;s lack of support of transparency). I then had to spend another day (50% of the development time) putting in deliberately WRONG numbers just to get things looking right in IE6.</p>
<p>My verdict is, it&#8217;s not worth supporting any more. Those organizations that prevent their users from running any other browser probably also restrict the kinds of sites they&#8217;re allowed to visit any way, so I wouldn&#8217;t worry about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Lane</title>
		<link>http://it.gen.nz/2008/09/13/bad-dog-ie6-bad-dog/comment-page-1/#comment-907</link>
		<dc:creator>Dave Lane</dc:creator>
		<pubDate>Sat, 13 Sep 2008 00:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=159#comment-907</guid>
		<description>Hello Colin,

For years (i.e. since it came out, about 7 years ago, I think), Micrsoft&#039;s Internet Explorer has been a source of frustration for web developers worldwide.  Web developers have published LOTS of pages helping other developers circumvent the multitude of inadequacies and proprietary quirks it foisted on the unsuspecting web user.  This site is a great example: http://www.positioniseverything.net/explorer.html 
A google for &quot;ie6 css problems&quot; returns 715,000 results.  My colleagues and I often discuss sending an invoice to Microsoft rather than forcing our web site customers to bear the cost of working around those IE6 problems, which can sometimes double the time required to create website.  I wouldn&#039;t be surprised if the international cost borne by businesses and organisations who, due to its lingering marketshare, still have to accommodate the fundamental brokenness of MS IE6, is in the tens or hundreds of billions of dollars.  To their credit, Facebook have recently announced that their new site engine will no longer support IE6, as doing so would have meant too big a compromise on their ability to offer innovative functionality.

The fact the some businesses and organisations still use IE6 is inexcusable given the multitude of better options that are &lt;em&gt;freely&lt;/em&gt; available (both free of cost, and free of the proprietary rubbish).  Those who still cling to IE6 are simply demonstrating their lack of savvy.  In most cases, their internal business systems (e.g. intranets) were built with dependencies on IE6-specific technologies (like Microsoft&#039;s proprietary security nightmare: &quot;ActiveX&quot;).  They are all shining examples of the foolishness of betting on the consistency of proprietary technologies, and the utter folly of equating &quot;big corporation&quot; with &quot;long term stability&quot;.</description>
		<content:encoded><![CDATA[<p>Hello Colin,</p>
<p>For years (i.e. since it came out, about 7 years ago, I think), Micrsoft&#8217;s Internet Explorer has been a source of frustration for web developers worldwide.  Web developers have published LOTS of pages helping other developers circumvent the multitude of inadequacies and proprietary quirks it foisted on the unsuspecting web user.  This site is a great example: <a href="http://www.positioniseverything.net/explorer.html" rel="nofollow">http://www.positioniseverything.net/explorer.html</a><br />
A google for &#8220;ie6 css problems&#8221; returns 715,000 results.  My colleagues and I often discuss sending an invoice to Microsoft rather than forcing our web site customers to bear the cost of working around those IE6 problems, which can sometimes double the time required to create website.  I wouldn&#8217;t be surprised if the international cost borne by businesses and organisations who, due to its lingering marketshare, still have to accommodate the fundamental brokenness of MS IE6, is in the tens or hundreds of billions of dollars.  To their credit, Facebook have recently announced that their new site engine will no longer support IE6, as doing so would have meant too big a compromise on their ability to offer innovative functionality.</p>
<p>The fact the some businesses and organisations still use IE6 is inexcusable given the multitude of better options that are <em>freely</em> available (both free of cost, and free of the proprietary rubbish).  Those who still cling to IE6 are simply demonstrating their lack of savvy.  In most cases, their internal business systems (e.g. intranets) were built with dependencies on IE6-specific technologies (like Microsoft&#8217;s proprietary security nightmare: &#8220;ActiveX&#8221;).  They are all shining examples of the foolishness of betting on the consistency of proprietary technologies, and the utter folly of equating &#8220;big corporation&#8221; with &#8220;long term stability&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

