<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>DOM Scripting comments: Clever comments</title>
        <link>http://domscripting.com/blog/display/14</link>
        <description>Aaron Gustafson has an article in the newest A List Apart. I really like the way he’s used comments.</description>
        <language>en</language>
        <item>
            <title>Aaron Gustafson</title>
            <link>http://domscripting.com/blog/display.php/14#comment34</link>
            <content:encoded><![CDATA[<p>I&#8217;m glad you appreciated that aspect of the article. Personally, I always feel a little slighted when I read an article about a great little script and there is no explanation whatsoever as to what the thought process is behind the code. IMHO, that is half of the learning value of an article or tutorial and it is something I always try and account for in my writing. I&#8217;m glad it didn&#8217;t go unnoticed.</p>

<p>As an aside, I recommend keeping these comments in your working version of every script, removing them only for the production version (along with any unnecessary whitespace).</p>
]]></content:encoded>
            <pubDate>Sat, 24 Sep 2005 19:38:16 GMT</pubDate>
        </item>
        <item>
            <title>!!blue</title>
            <link>http://domscripting.com/blog/display.php/14#comment33</link>
            <content:encoded><![CDATA[<p>Awww, don&#8217;t feel bad, it happens to the best of us. I know I&#8217;ve looked back on projects and thought the exact same thing. </p>

<p>Looking forward to getting your book in the mail! ;)</p>
]]></content:encoded>
            <pubDate>Fri, 23 Sep 2005 20:48:17 GMT</pubDate>
        </item>
   </channel>
</rss>