<?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: JSON == YAML? It&#8217;s getting closer to truth</title>
	<atom:link href="http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Paddy</title>
		<link>http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth/comment-page-1#comment-3646</link>
		<dc:creator>Paddy</dc:creator>
		<pubDate>Sat, 18 Feb 2006 18:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/json-yaml-its-getting-closer-to-truth#comment-3646</guid>
		<description>Oh well,
i thought one of the good things about YAML was that the indentation made it easier to read and so maintain. I had seen so many xml examples where the xml was pretty-printed, yet so many real world xml files that were muged-up into as few lines as they could get away with.

Now I find that correct indentation is optional in YAML too. Oh well...</description>
		<content:encoded><![CDATA[<p>Oh well,<br />
i thought one of the good things about YAML was that the indentation made it easier to read and so maintain. I had seen so many xml examples where the xml was pretty-printed, yet so many real world xml files that were muged-up into as few lines as they could get away with.</p>
<p>Now I find that correct indentation is optional in YAML too. Oh well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Wood</title>
		<link>http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth/comment-page-1#comment-1594</link>
		<dc:creator>Tim Wood</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/json-yaml-its-getting-closer-to-truth#comment-1594</guid>
		<description>No YAML tags on this site and I suspect none on most of the sites I watch.  Google was kind enough to explain the acronym (&quot;Yet another markup language&quot;) and point me at http://www.yaml.org/ for a definition:

YAML(tm) (rhymes with &quot;camel&quot;) is a straightforward machine parsable data serialization format designed for human readability and interaction with scripting languages such as Perl and Python. YAML is optimized for data serialization, configuration settings, log files, Internet messaging and filtering.

Okay, so what?  I hate to be harsh, because this is a really cool example of project teams (apparently the JSON one in this case) working to make programmer&#039;s lives easier.  While that&#039;s cool, the article doesn&#039;t &#039;splain what difference this is going to make in my work.</description>
		<content:encoded><![CDATA[<p>No YAML tags on this site and I suspect none on most of the sites I watch.  Google was kind enough to explain the acronym (&#8220;Yet another markup language&#8221;) and point me at <a href="http://www.yaml.org/" rel="nofollow">http://www.yaml.org/</a> for a definition:</p>
<p>YAML(tm) (rhymes with &#8220;camel&#8221;) is a straightforward machine parsable data serialization format designed for human readability and interaction with scripting languages such as Perl and Python. YAML is optimized for data serialization, configuration settings, log files, Internet messaging and filtering.</p>
<p>Okay, so what?  I hate to be harsh, because this is a really cool example of project teams (apparently the JSON one in this case) working to make programmer&#8217;s lives easier.  While that&#8217;s cool, the article doesn&#8217;t &#8216;splain what difference this is going to make in my work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dion Almaer</title>
		<link>http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth/comment-page-1#comment-1595</link>
		<dc:creator>Dion Almaer</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/json-yaml-its-getting-closer-to-truth#comment-1595</guid>
		<description>Tim

You are right. YAML originally took off in the Ruby community as a better XML (for some things. right tool for the job).

If you think about all of the formats that you have to deal with there are tons.

More frameworks are using YAML these days. A lot more frameworks are using JSON as a way to pass things around (so much faster than XML).

If these combine, then the tools that we have for one, instantly work for the other (and vince versa).

More interop, better tools. It&#039;s all good.

Dion</description>
		<content:encoded><![CDATA[<p>Tim</p>
<p>You are right. YAML originally took off in the Ruby community as a better XML (for some things. right tool for the job).</p>
<p>If you think about all of the formats that you have to deal with there are tons.</p>
<p>More frameworks are using YAML these days. A lot more frameworks are using JSON as a way to pass things around (so much faster than XML).</p>
<p>If these combine, then the tools that we have for one, instantly work for the other (and vince versa).</p>
<p>More interop, better tools. It&#8217;s all good.</p>
<p>Dion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Cheng</title>
		<link>http://ajaxian.com/archives/json-yaml-its-getting-closer-to-truth/comment-page-1#comment-1596</link>
		<dc:creator>Michael Cheng</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://test.ajaxian.com/archives/json-yaml-its-getting-closer-to-truth#comment-1596</guid>
		<description>I agree with you.

if different technology can interop or interchangable, the world will be better for us.
</description>
		<content:encoded><![CDATA[<p>I agree with you.</p>
<p>if different technology can interop or interchangable, the world will be better for us.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

