<?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: I *heart* plain text configuration files</title>
	<atom:link href="http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/</link>
	<description>Man bites Ogre</description>
	<lastBuildDate>Thu, 09 Feb 2012 08:49:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/comment-page-1/#comment-249465</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 04 Feb 2009 10:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=1366#comment-249465</guid>
		<description>I&#039;m not a big fan of XML for configuration files. They&#039;re harder to read than plain text - sure, if you use a dedicated XML editor then they&#039;re easy to collapse &amp; parse, have autocomplete for etc - that&#039;s good. But the point of this was that text has a very low overhead and is easy to examine regardless of what tools I have available.

The Java servers I used to run *lived* on XML configuration files. Nice idea, came about precisely from the reasons you describe, but it&#039;s honestly not easier in practice than plain text, IMO. XML is better than custom registries and data formats though.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not a big fan of XML for configuration files. They&#8217;re harder to read than plain text &#8211; sure, if you use a dedicated XML editor then they&#8217;re easy to collapse &#038; parse, have autocomplete for etc &#8211; that&#8217;s good. But the point of this was that text has a very low overhead and is easy to examine regardless of what tools I have available.</p>
<p>The Java servers I used to run *lived* on XML configuration files. Nice idea, came about precisely from the reasons you describe, but it&#8217;s honestly not easier in practice than plain text, IMO. XML is better than custom registries and data formats though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ASpanishGuy</title>
		<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/comment-page-1/#comment-249429</link>
		<dc:creator>ASpanishGuy</dc:creator>
		<pubDate>Tue, 03 Feb 2009 23:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=1366#comment-249429</guid>
		<description>I **LOVE** Markdown to write my docs. XML is not Human readable. Latex is very difficult and easy to forget if you don&#039;t write someting for long time. So... Yes, i agree: Plain text files rocks for writing docs and configs and anything...

PD: I know that it&#039;s a bit off topic, but when i read *heart* and plain text files. I have the need to write something.
PD2: Check this program: http://johnmacfarlane.net/pandoc/</description>
		<content:encoded><![CDATA[<p>I **LOVE** Markdown to write my docs. XML is not Human readable. Latex is very difficult and easy to forget if you don&#8217;t write someting for long time. So&#8230; Yes, i agree: Plain text files rocks for writing docs and configs and anything&#8230;</p>
<p>PD: I know that it&#8217;s a bit off topic, but when i read *heart* and plain text files. I have the need to write something.<br />
PD2: Check this program: <a href="http://johnmacfarlane.net/pandoc/" rel="nofollow">http://johnmacfarlane.net/pandoc/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Evans</title>
		<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/comment-page-1/#comment-249416</link>
		<dc:creator>Paul Evans</dc:creator>
		<pubDate>Tue, 03 Feb 2009 21:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=1366#comment-249416</guid>
		<description>.Net stuff tends to encourage xml configuration and I expect a lot of Windows apps will go that way myself.

Course xml is much more verbose than plain text, but it is easy to validate, collapse in to sections, etc.</description>
		<content:encoded><![CDATA[<p>.Net stuff tends to encourage xml configuration and I expect a lot of Windows apps will go that way myself.</p>
<p>Course xml is much more verbose than plain text, but it is easy to validate, collapse in to sections, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/comment-page-1/#comment-249411</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 03 Feb 2009 18:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=1366#comment-249411</guid>
		<description>Yeah, that&#039;s good for a fast restore back to a previous point, but it&#039;s much like a regular backup or image replication (just more convenient). Wasn&#039;t really the point of this diatribe :)</description>
		<content:encoded><![CDATA[<p>Yeah, that&#8217;s good for a fast restore back to a previous point, but it&#8217;s much like a regular backup or image replication (just more convenient). Wasn&#8217;t really the point of this diatribe <img src='http://www.stevestreeting.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Poo Bear</title>
		<link>http://www.stevestreeting.com/2009/02/03/i-heart-plain-text-configuration-files/comment-page-1/#comment-249408</link>
		<dc:creator>Poo Bear</dc:creator>
		<pubDate>Tue, 03 Feb 2009 18:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevestreeting.com/?p=1366#comment-249408</guid>
		<description>One neat trick. Set up the physical server to host virtual servers then host your site as a VM. 

To transfer from one physical machine to another:
   1. shut down VM
   2. compacted and compressed it
   3. transfer it to the new server
   4. booted it up again 
   5. change IP

Backing up and restoring is a similar process.</description>
		<content:encoded><![CDATA[<p>One neat trick. Set up the physical server to host virtual servers then host your site as a VM. </p>
<p>To transfer from one physical machine to another:<br />
   1. shut down VM<br />
   2. compacted and compressed it<br />
   3. transfer it to the new server<br />
   4. booted it up again<br />
   5. change IP</p>
<p>Backing up and restoring is a similar process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

