<?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: JavaScript Can Learn: Now Teach It Tricks!</title>
	<atom:link href="http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/</link>
	<description></description>
	<lastBuildDate>Tue, 17 Jan 2012 16:57:58 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Javascript Ninja</title>
		<link>http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/comment-page-1/#comment-4967</link>
		<dc:creator>Javascript Ninja</dc:creator>
		<pubDate>Mon, 18 Apr 2011 06:53:54 +0000</pubDate>
		<guid isPermaLink="false">http://fuelyourcoding.com/?p=672#comment-4967</guid>
		<description>One mis-feature that is often used is to extend Object.prototype or one of the other built in prototypes.

This technique is called monkey patching(http://en.wikipedia.org/wiki/Monkey_patch) and breaks encapsulation. While used by widely spread frameworks such as Prototype, there is still no good reason for cluttering built-in types with additional non-standard functionality.

The only good reason for extending a built-in prototype is to backport the features of newer JavaScript engines; for example, Array.forEach.

Further, the native prototypes should never be extended unless it is for the sake of compatibility with newer JavaScript features.</description>
		<content:encoded><![CDATA[<p>One mis-feature that is often used is to extend Object.prototype or one of the other built in prototypes.</p>
<p>This technique is called monkey patching(http://en.wikipedia.org/wiki/Monkey_patch) and breaks encapsulation. While used by widely spread frameworks such as Prototype, there is still no good reason for cluttering built-in types with additional non-standard functionality.</p>
<p>The only good reason for extending a built-in prototype is to backport the features of newer JavaScript engines; for example, Array.forEach.</p>
<p>Further, the native prototypes should never be extended unless it is for the sake of compatibility with newer JavaScript features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/comment-page-1/#comment-1926</link>
		<dc:creator>William</dc:creator>
		<pubDate>Wed, 17 Feb 2010 11:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://fuelyourcoding.com/?p=672#comment-1926</guid>
		<description>Great tricks! 

I am new to javascript and this really opened my mind. Thanks</description>
		<content:encoded><![CDATA[<p>Great tricks! </p>
<p>I am new to javascript and this really opened my mind. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Friday FUEL Fix (11/06/09) &#124; Fuel Your Creativity</title>
		<link>http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/comment-page-1/#comment-1143</link>
		<dc:creator>Friday FUEL Fix (11/06/09) &#124; Fuel Your Creativity</dc:creator>
		<pubDate>Fri, 06 Nov 2009 10:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://fuelyourcoding.com/?p=672#comment-1143</guid>
		<description>[...] Check out this fine post from Fuel Your Coding JavaScript Can Learn: Now Teach It Tricks! [...]</description>
		<content:encoded><![CDATA[<p>[...] Check out this fine post from Fuel Your Coding JavaScript Can Learn: Now Teach It Tricks! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerod Santo</title>
		<link>http://fuelyourcoding.com/javascript-can-learn-now-teach-it-tricks/comment-page-1/#comment-1109</link>
		<dc:creator>Jerod Santo</dc:creator>
		<pubDate>Fri, 30 Oct 2009 13:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://fuelyourcoding.com/?p=672#comment-1109</guid>
		<description>Great read, Doug. I had never had the prototype object explained to me before. Thanks!

I know what you mean when you say that switching languages between client &amp; server can be tough sometimes. It is apparent to me that JavaScript wins on the client-side (and will win even bigger in the near future), so I&#039;m excited about some of the server-side JavaScript projects like Jack.

Perhaps server-side JavaScript would be an interesting topic for a future post.

Cheers!</description>
		<content:encoded><![CDATA[<p>Great read, Doug. I had never had the prototype object explained to me before. Thanks!</p>
<p>I know what you mean when you say that switching languages between client &amp; server can be tough sometimes. It is apparent to me that JavaScript wins on the client-side (and will win even bigger in the near future), so I&#8217;m excited about some of the server-side JavaScript projects like Jack.</p>
<p>Perhaps server-side JavaScript would be an interesting topic for a future post.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

