<?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: WS-Configuration</title>
	<atom:link href="http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/feed/" rel="self" type="application/rss+xml" />
	<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/</link>
	<description></description>
	<lastBuildDate>Sun, 15 Jan 2012 21:29:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: apotheon</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137669</link>
		<dc:creator>apotheon</dc:creator>
		<pubDate>Sat, 03 Mar 2007 02:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137669</guid>
		<description>I&#039;m a fan of using either YAML or an S-expression syntax for config files -- YAML because there isn&#039;t much pre-built support for S-expression config syntax out there, and I haven&#039;t gotten around to building my own portable libraries for it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a fan of using either YAML or an S-expression syntax for config files &#8212; YAML because there isn&#8217;t much pre-built support for S-expression config syntax out there, and I haven&#8217;t gotten around to building my own portable libraries for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137661</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Thu, 01 Mar 2007 08:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137661</guid>
		<description>My beef with XML configuration files is not addressed with simple configuration files, Java properties files, or (yuck) YAML.  It&#039;s the lack of complete specification that irks me.  The DTD, XML Schema, or ad hoc specification doesn&#039;t truly encapsulate what the application expects, so I can provide &quot;valid&quot; input and receive unexpected (i.e., invalid) behavior.  I would suggest something like Schematron, but at that point we&#039;re essentially using a programming language as an extension to the application when it should just be written in the same language as the application in the first place...

Or maybe I&#039;ve been using Emacs too much.</description>
		<content:encoded><![CDATA[<p>My beef with XML configuration files is not addressed with simple configuration files, Java properties files, or (yuck) YAML.  It&#8217;s the lack of complete specification that irks me.  The DTD, XML Schema, or ad hoc specification doesn&#8217;t truly encapsulate what the application expects, so I can provide &#8220;valid&#8221; input and receive unexpected (i.e., invalid) behavior.  I would suggest something like Schematron, but at that point we&#8217;re essentially using a programming language as an extension to the application when it should just be written in the same language as the application in the first place&#8230;</p>
<p>Or maybe I&#8217;ve been using Emacs too much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Norris</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137660</link>
		<dc:creator>Andrew Norris</dc:creator>
		<pubDate>Thu, 01 Mar 2007 05:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137660</guid>
		<description>joe,

Thanks for the defmacro link. I&#039;m already a convert, but that&#039;s the best explanation of lisp for non-lispers that I&#039;ve ever seen -- I&#039;ll definitely be passing that one along.

And here&#039;s another resounding vote for &quot;XML sucks.&quot;</description>
		<content:encoded><![CDATA[<p>joe,</p>
<p>Thanks for the defmacro link. I&#8217;m already a convert, but that&#8217;s the best explanation of lisp for non-lispers that I&#8217;ve ever seen &#8212; I&#8217;ll definitely be passing that one along.</p>
<p>And here&#8217;s another resounding vote for &#8220;XML sucks.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137658</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Wed, 28 Feb 2007 21:13:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137658</guid>
		<description>For anyone interested, here&#039;s a longish but good article about using s-expressions instead of xml...as an intro to Lisp, for people who don&#039;t get what all the parens are for.
http://www.defmacro.org/ramblings/lisp.html</description>
		<content:encoded><![CDATA[<p>For anyone interested, here&#8217;s a longish but good article about using s-expressions instead of xml&#8230;as an intro to Lisp, for people who don&#8217;t get what all the parens are for.<br />
<a href="http://www.defmacro.org/ramblings/lisp.html" rel="nofollow">http://www.defmacro.org/ramblings/lisp.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Allen</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137657</link>
		<dc:creator>Jonathan Allen</dc:creator>
		<pubDate>Wed, 28 Feb 2007 21:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137657</guid>
		<description>With MS adding XML support to VB at the language level, I expect the pain factor for me to drop significantly. But as it stand, I perfer short, clean flat files.

Some people I worked with actually used VBScript files for configuration. When you write &quot;m_Config.ServerTimeout = 50&quot;, that is literally what you get, no questions asked.</description>
		<content:encoded><![CDATA[<p>With MS adding XML support to VB at the language level, I expect the pain factor for me to drop significantly. But as it stand, I perfer short, clean flat files.</p>
<p>Some people I worked with actually used VBScript files for configuration. When you write &#8220;m_Config.ServerTimeout = 50&#8243;, that is literally what you get, no questions asked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137656</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 28 Feb 2007 21:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137656</guid>
		<description>In a way I agree, but after using things like SimpleXML (PHP) and especially Amara (Python), XML based configs are simple and easy to work with. With that said, I have found nothing even close in the .NET world (given I haven&#039;t looked to hard), YMMV.</description>
		<content:encoded><![CDATA[<p>In a way I agree, but after using things like SimpleXML (PHP) and especially Amara (Python), XML based configs are simple and easy to work with. With that said, I have found nothing even close in the .NET world (given I haven&#8217;t looked to hard), YMMV.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137655</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Wed, 28 Feb 2007 20:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137655</guid>
		<description>@daniel,

Not at all. I routinely get my commands, and regular expressions, and most everything else I write wrong, so I just check it and fix it.

But when I get it wrong with XML, finding and fixing these errors sucks more time out of my day. So I&#039;m going to leave this glaring error in the post as is.</description>
		<content:encoded><![CDATA[<p>@daniel,</p>
<p>Not at all. I routinely get my commands, and regular expressions, and most everything else I write wrong, so I just check it and fix it.</p>
<p>But when I get it wrong with XML, finding and fixing these errors sucks more time out of my day. So I&#8217;m going to leave this glaring error in the post as is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137654</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 28 Feb 2007 20:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137654</guid>
		<description>Would you be mad if I pointed out that sed command would give you an empty file? Try sed -i ;)</description>
		<content:encoded><![CDATA[<p>Would you be mad if I pointed out that sed command would give you an empty file? Try sed -i ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engtech</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137653</link>
		<dc:creator>engtech</dc:creator>
		<pubDate>Wed, 28 Feb 2007 19:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137653</guid>
		<description>I agree with you so whole-heartedly.

I bought into the XML config file buzz around 2002, switched a bunch of internal projects to it and then had to deal with how often engineers would screw up the XML when editing it by hand.

I&#039;ve switched to YAML as well and I&#039;m loving it.</description>
		<content:encoded><![CDATA[<p>I agree with you so whole-heartedly.</p>
<p>I bought into the XML config file buzz around 2002, switched a bunch of internal projects to it and then had to deal with how often engineers would screw up the XML when editing it by hand.</p>
<p>I&#8217;ve switched to YAML as well and I&#8217;m loving it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/comment-page-1/#comment-137652</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Wed, 28 Feb 2007 06:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/02/27/xml-configs-files-are-your-competitive-disadvantage/#comment-137652</guid>
		<description>For most stuff, simple text formats work extremely well. I&#039;ve been using Java property files and UN*X configuration files for years, with no apparent brain damage.

As a rough estimate
  find /etc &#124; wc -l 
returns 2470, not all of which are configuration files, mind you.

For more complex stuff, I&#039;d go with YAML which has the structure, but is much easier to handle than XML. Especially if you ever need to edit it.

For really complex stuff, I&#039;d consider why it has to be that complex.

And, I&#039;m finding a surprising number of places where code works better than static files, especially code that in its simplest form doesn&#039;t look much different from regular text files. The for loop is a wonderful way to eliminate redundancy.</description>
		<content:encoded><![CDATA[<p>For most stuff, simple text formats work extremely well. I&#8217;ve been using Java property files and UN*X configuration files for years, with no apparent brain damage.</p>
<p>As a rough estimate<br />
  find /etc | wc -l<br />
returns 2470, not all of which are configuration files, mind you.</p>
<p>For more complex stuff, I&#8217;d go with YAML which has the structure, but is much easier to handle than XML. Especially if you ever need to edit it.</p>
<p>For really complex stuff, I&#8217;d consider why it has to be that complex.</p>
<p>And, I&#8217;m finding a surprising number of places where code works better than static files, especially code that in its simplest form doesn&#8217;t look much different from regular text files. The for loop is a wonderful way to eliminate redundancy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

