<?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: IE vs. Standards</title>
	<atom:link href="http://www.davinciunltd.com/2008/03/ie-vs-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davinciunltd.com/2008/03/ie-vs-standards/</link>
	<description>Jim McKeeth's blog on creative and innovative Delphi programming.</description>
	<pubDate>Tue, 02 Dec 2008 23:17:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: d.cornelius</title>
		<link>http://www.davinciunltd.com/2008/03/ie-vs-standards/#comment-148</link>
		<dc:creator>d.cornelius</dc:creator>
		<pubDate>Sun, 30 Mar 2008 05:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.davinciunltd.com/2008/03/ie-vs-standards/#comment-148</guid>
		<description>I'm a "best practices" person, so I'll always vote for the idealistic method.  Yeah, it's gonna hurt; yeah, there will be pages that won't work any more; yeah, there's going to be lots of effort to fix everything.  Too bad, it should've been done right in the first place.  Or maybe it's not that it wasn't done right in the first place, but that there's just a newer, better way to do it and we should throw away the old code.  It's helpful to review everything once in a while anyway.

The content management system I chose to build my web site in, Drupal, is based on this concept.  I recently had to do a major overhaul of my site and a client's site just to get them to up-to-date with the latest version of Drupal so that the site would be ready for PHP 5.  I'd rather have to do that work and know I'm keeping up with technology, than to have to bring along baggage of old routines.

There was an unexepected benefit of updating the web sites.  I learned about some new modules that were available and changed the data structures to accomodate them which will actually give me more flexibility.  If I hadn't needed to update the sites, I wouldn't have discovered these new features.

And I have dealt with changed Indy functions in a Delphi program.  I work for a boss that only cares if it is working--we gotta move on to the next project ("if the old version worked, and we have a program similar to this new project, copy it and make it work.").  Every fiber of me goes against that concept.  However, it's also why I'm not in business for myself anymore.  I spent too much time "doing it right" rather than "getting it done."</description>
		<content:encoded><![CDATA[<p>I&#8217;m a &#8220;best practices&#8221; person, so I&#8217;ll always vote for the idealistic method.  Yeah, it&#8217;s gonna hurt; yeah, there will be pages that won&#8217;t work any more; yeah, there&#8217;s going to be lots of effort to fix everything.  Too bad, it should&#8217;ve been done right in the first place.  Or maybe it&#8217;s not that it wasn&#8217;t done right in the first place, but that there&#8217;s just a newer, better way to do it and we should throw away the old code.  It&#8217;s helpful to review everything once in a while anyway.</p>
<p>The content management system I chose to build my web site in, Drupal, is based on this concept.  I recently had to do a major overhaul of my site and a client&#8217;s site just to get them to up-to-date with the latest version of Drupal so that the site would be ready for PHP 5.  I&#8217;d rather have to do that work and know I&#8217;m keeping up with technology, than to have to bring along baggage of old routines.</p>
<p>There was an unexepected benefit of updating the web sites.  I learned about some new modules that were available and changed the data structures to accomodate them which will actually give me more flexibility.  If I hadn&#8217;t needed to update the sites, I wouldn&#8217;t have discovered these new features.</p>
<p>And I have dealt with changed Indy functions in a Delphi program.  I work for a boss that only cares if it is working&#8211;we gotta move on to the next project (&#8221;if the old version worked, and we have a program similar to this new project, copy it and make it work.&#8221;).  Every fiber of me goes against that concept.  However, it&#8217;s also why I&#8217;m not in business for myself anymore.  I spent too much time &#8220;doing it right&#8221; rather than &#8220;getting it done.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xepol</title>
		<link>http://www.davinciunltd.com/2008/03/ie-vs-standards/#comment-147</link>
		<dc:creator>Xepol</dc:creator>
		<pubDate>Sat, 29 Mar 2008 18:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.davinciunltd.com/2008/03/ie-vs-standards/#comment-147</guid>
		<description>Short term pain for long term gain.  About time someone embraced the concept.

Doesn't matter what MS does anymore, the same people bitch.  They don't even care if they make sense anymore.  IE doesn't adhear to standards and breaks everything, IE adhears to standards and breaks everything.

It isn't about the pragmatists vs the idealist, it is all about bashing MS.  Enough is bloody enough.</description>
		<content:encoded><![CDATA[<p>Short term pain for long term gain.  About time someone embraced the concept.</p>
<p>Doesn&#8217;t matter what MS does anymore, the same people bitch.  They don&#8217;t even care if they make sense anymore.  IE doesn&#8217;t adhear to standards and breaks everything, IE adhears to standards and breaks everything.</p>
<p>It isn&#8217;t about the pragmatists vs the idealist, it is all about bashing MS.  Enough is bloody enough.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
