<?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 Harmony: The JS Train Is Moving</title>
	<atom:link href="http://almaer.com/blog/javascript-harmony-the-js-train-is-moving/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/javascript-harmony-the-js-train-is-moving</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brendan Eich</title>
		<link>http://almaer.com/blog/javascript-harmony-the-js-train-is-moving/comment-page-1#comment-47888</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Fri, 21 Jan 2011 17:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2931#comment-47888</guid>
		<description>Hi Dion, thanks for the kind words. One thing to add: Douglas&#039;s advice has the advantage that it will continue to work for a long time. Writing scripts that work in old and new browsers will mean writing in the &quot;JS-in-reality&quot; dialect, or using a translator from Harmony for old browsers while loading directly in new, or of course using CoffeeScript or another language front end.

For the &quot;JS-in-reality&quot;, Crock&#039;s advice works, and I don&#039;t see us ever breaking things there except around the edges, and in good ways like typeof null, and using only one hand&#039;s fingers to count the breaks.

/be</description>
		<content:encoded><![CDATA[<p>Hi Dion, thanks for the kind words. One thing to add: Douglas&#8217;s advice has the advantage that it will continue to work for a long time. Writing scripts that work in old and new browsers will mean writing in the &#8220;JS-in-reality&#8221; dialect, or using a translator from Harmony for old browsers while loading directly in new, or of course using CoffeeScript or another language front end.</p>
<p>For the &#8220;JS-in-reality&#8221;, Crock&#8217;s advice works, and I don&#8217;t see us ever breaking things there except around the edges, and in good ways like typeof null, and using only one hand&#8217;s fingers to count the breaks.</p>
<p>/be</p>
]]></content:encoded>
	</item>
</channel>
</rss>
