<?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: Ten good practices for writing JavaScript in 2005</title>
	<atom:link href="http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Tue, 02 Dec 2008 07:39:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Ian Bicking</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3955</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3955</guid>
		<description>&lt;p&gt;He advocates short variable names to keep your Javascript speedy.  I don't know what to make of that.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>He advocates short variable names to keep your Javascript speedy.  I don&#8217;t know what to make of that.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: thody</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3956</link>
		<dc:creator>thody</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3956</guid>
		<description>&lt;p&gt;Yeah...that one kind of raised my ears too. The rest of it was pretty helpful though. I like where I see Javascript going these days.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Yeah&#8230;that one kind of raised my ears too. The rest of it was pretty helpful though. I like where I see Javascript going these days.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: someonewhois</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3957</link>
		<dc:creator>someonewhois</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3957</guid>
		<description>&lt;p&gt;Maybe he means small file names to save bandwidth? Beats me.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Maybe he means small file names to save bandwidth? Beats me.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: wranga</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3958</link>
		<dc:creator>wranga</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3958</guid>
		<description>&lt;p&gt;Maybe because Javascript isn't compiled longer variable names have an impact on it's speed. I wouldn't think that the impact would be that significant,  though.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Maybe because Javascript isn&#8217;t compiled longer variable names have an impact on it&#8217;s speed. I wouldn&#8217;t think that the impact would be that significant,  though.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ChiliJ</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3959</link>
		<dc:creator>ChiliJ</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3959</guid>
		<description>&lt;p&gt;It's probably bandwidth. But, sacrificing readability for the sake of a little bandwidth in not really good practice. People concerned with bandwidth should run their script through a compressor/obfuscator, which could strip unnecessary spaces and comments, including changing of variable names.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>It&#8217;s probably bandwidth. But, sacrificing readability for the sake of a little bandwidth in not really good practice. People concerned with bandwidth should run their script through a compressor/obfuscator, which could strip unnecessary spaces and comments, including changing of variable names.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bsluis</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3960</link>
		<dc:creator>bsluis</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3960</guid>
		<description>&lt;p&gt;What I meant is that the size of the JS file impacts the speed of the download, which on its turn may impact the speed the unobtrusive behavior gets attached.&lt;/p&gt;

&lt;p&gt;I agree that keeping variable names short (using myVar instead of myVeryDescriptiveVar) doesn't have a significant impact on the download speed of the JS file by itself, however the total of using short variable names, condensing code before deployment, short straightforward code, HTTP compression, etc. will.&lt;/p&gt;

&lt;p&gt;But point taken, it was short on context and it probably shouldn't have been a seperate bullet at all. Hope this answered your questions.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>What I meant is that the size of the JS file impacts the speed of the download, which on its turn may impact the speed the unobtrusive behavior gets attached.</p>
<p>I agree that keeping variable names short (using myVar instead of myVeryDescriptiveVar) doesn&#8217;t have a significant impact on the download speed of the JS file by itself, however the total of using short variable names, condensing code before deployment, short straightforward code, HTTP compression, etc. will.</p>
<p>But point taken, it was short on context and it probably shouldn&#8217;t have been a seperate bullet at all. Hope this answered your questions.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Octal</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3961</link>
		<dc:creator>Octal</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3961</guid>
		<description>&lt;p&gt;As Bruce Lee said; "Knowing is not enough, we must apply. Willing is not enough we must do."&lt;/p&gt;

&lt;p&gt;Nice tips there bsluis&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>As Bruce Lee said; &#8220;Knowing is not enough, we must apply. Willing is not enough we must do.&#8221;</p>
<p>Nice tips there bsluis</p>]]></content:encoded>
	</item>
	<item>
		<title>By: wei</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3962</link>
		<dc:creator>wei</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3962</guid>
		<description>&lt;p&gt;You can alway compress the javascript for production.&lt;/p&gt;

&lt;p&gt;Free tool&lt;br /&gt;
http://www.saltstorm.net/depo/esc/introduction.wbm&lt;br /&gt;
&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>You can alway compress the javascript for production.</p>
<p>Free tool<br />
<a href="http://www.saltstorm.net/depo/esc/introduction.wbm" rel="nofollow">http://www.saltstorm.net/depo/esc/introduction.wbm</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3963</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3963</guid>
		<description>&lt;p&gt;"however the total of using short variable names, condensing code before deployment, short straightforward code, HTTP compression, etc. will."&lt;/p&gt;

&lt;p&gt;huh? compression will negate the difference between short names and long variable names: regardless of the length of a variable name, in compressed text it'll be represented by a single token.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>&#8220;however the total of using short variable names, condensing code before deployment, short straightforward code, HTTP compression, etc. will.&#8221;</p>
<p>huh? compression will negate the difference between short names and long variable names: regardless of the length of a variable name, in compressed text it&#8217;ll be represented by a single token.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Kadence</title>
		<link>http://www.sitepoint.com/blogs/2005/04/19/ten-good-practices-for-writing-javascript-in-2005/#comment-3964</link>
		<dc:creator>Kadence</dc:creator>
		<pubDate>Wed, 31 Dec 1969 19:00:00 +0000</pubDate>
		<guid isPermaLink="false">272191875#comment-3964</guid>
		<description>&lt;p&gt;&lt;blockquote&gt;&lt;p&gt;But, sacrificing readability for the sake of a little bandwidth in not really good practice.&lt;/p&gt;&lt;/blockquote&gt;&lt;br /&gt;
I agree with this.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>
<blockquote>
<p>But, sacrificing readability for the sake of a little bandwidth in not really good practice.</p>
</blockquote>
</p><p>
I agree with this.</p>]]></content:encoded>
	</item>
</channel>
</rss>
