<?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: ECMAScript Harmony: New Life for JavaScript</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 18:39:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sfrost2004</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-783562</link>
		<dc:creator>sfrost2004</dc:creator>
		<pubDate>Wed, 20 Aug 2008 21:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-783562</guid>
		<description>&quot;writing standards and hoping that the browsers will follow doesn’t work...With HTML 5, the W3C is letting the browsers try out new ideas, and is forging standards from the good stuff&quot;

So does this mean that the &quot;traditional&quot; way of creating standards has been turned on it&#039;s head? Whereas standards were once created by global bodies and the industry had to seek to &quot;achieve&quot; those standards, it sounds like the industry can now do what it likes and the standards are just a collation of the best bits.

This sounds to me like web standards are becoming less of a gold standard (no pun intended) for good web development practice and more of an excuse for ratifying new browser features. What I&#039;m worried about is that the less exciting or more difficult aspects of web standards (like promoting accessibility) will be gradually forgotten and left behind.</description>
		<content:encoded><![CDATA[<p>&#8220;writing standards and hoping that the browsers will follow doesn’t work&#8230;With HTML 5, the W3C is letting the browsers try out new ideas, and is forging standards from the good stuff&#8221;</p>
<p>So does this mean that the &#8220;traditional&#8221; way of creating standards has been turned on it&#8217;s head? Whereas standards were once created by global bodies and the industry had to seek to &#8220;achieve&#8221; those standards, it sounds like the industry can now do what it likes and the standards are just a collation of the best bits.</p>
<p>This sounds to me like web standards are becoming less of a gold standard (no pun intended) for good web development practice and more of an excuse for ratifying new browser features. What I&#8217;m worried about is that the less exciting or more difficult aspects of web standards (like promoting accessibility) will be gradually forgotten and left behind.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Lowe</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-783480</link>
		<dc:creator>Brian Lowe</dc:creator>
		<pubDate>Wed, 20 Aug 2008 18:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-783480</guid>
		<description>Wait though...

I thought the W3C included representation from the major players, so surely the big browsers have a pretty loud voice when it comes to defining the &#039;standard&#039;.

If the W3C doesn&#039;t already include Mozilla and Microsoft reps then it has been wasting its time.</description>
		<content:encoded><![CDATA[<p>Wait though&#8230;</p>
<p>I thought the W3C included representation from the major players, so surely the big browsers have a pretty loud voice when it comes to defining the &#8217;standard&#8217;.</p>
<p>If the W3C doesn&#8217;t already include Mozilla and Microsoft reps then it has been wasting its time.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Borozdin</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-783476</link>
		<dc:creator>Mike Borozdin</dc:creator>
		<pubDate>Wed, 20 Aug 2008 18:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-783476</guid>
		<description>So, what will be changed in the new version of JavaScript?</description>
		<content:encoded><![CDATA[<p>So, what will be changed in the new version of JavaScript?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: anonymous3</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-783421</link>
		<dc:creator>anonymous3</dc:creator>
		<pubDate>Wed, 20 Aug 2008 16:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-783421</guid>
		<description>Maybe the W3C should create a browser.</description>
		<content:encoded><![CDATA[<p>Maybe the W3C should create a browser.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: seyDoggy</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-783162</link>
		<dc:creator>seyDoggy</dc:creator>
		<pubDate>Wed, 20 Aug 2008 03:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-783162</guid>
		<description>This is good news in my view. W3C has done one thing if nothing else, raised the awareness around why standards should exist. Maybe their approach was a bit too intense but look at what it&#039;s done for the web experience as a whole. I hope TC39 and their new found love for each other can do the same for javascript.</description>
		<content:encoded><![CDATA[<p>This is good news in my view. W3C has done one thing if nothing else, raised the awareness around why standards should exist. Maybe their approach was a bit too intense but look at what it&#8217;s done for the web experience as a whole. I hope TC39 and their new found love for each other can do the same for javascript.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: mattymcg</title>
		<link>http://www.sitepoint.com/blogs/2008/08/19/ecmascript-harmony-new-life-for-javascript/comment-page-1/#comment-782775</link>
		<dc:creator>mattymcg</dc:creator>
		<pubDate>Tue, 19 Aug 2008 12:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=2853#comment-782775</guid>
		<description>Good food for thought, Kev. We wouldn&#039;t have Ajax if Microsoft hadn&#039;t pushed the envelope in IE so many years ago. I disagree a bit with this statement though (which, I suppose, is actually the crux of your argument):

&lt;blockquote&gt;writing standards and hoping that the browsers will follow doesn’t work&lt;/blockquote&gt;

By the same token, allowing browser vendors a free-for-all and hoping that they&#039;ll permit themselves to be reigned in doesn&#039;t work either -- this is the exact situation that resulted in the so-called &quot;browser wars&quot;, ActiveX and the death of Netscape.

It needs to be a bit of both. Measured innovation, if you will. The W3C still has a place, it&#039;s just not the one-way process they&#039;ve always attempted to make it.</description>
		<content:encoded><![CDATA[<p>Good food for thought, Kev. We wouldn&#8217;t have Ajax if Microsoft hadn&#8217;t pushed the envelope in IE so many years ago. I disagree a bit with this statement though (which, I suppose, is actually the crux of your argument):</p>
<blockquote><p>writing standards and hoping that the browsers will follow doesn’t work</p></blockquote>
<p>By the same token, allowing browser vendors a free-for-all and hoping that they&#8217;ll permit themselves to be reigned in doesn&#8217;t work either &#8212; this is the exact situation that resulted in the so-called &#8220;browser wars&#8221;, ActiveX and the death of Netscape.</p>
<p>It needs to be a bit of both. Measured innovation, if you will. The W3C still has a place, it&#8217;s just not the one-way process they&#8217;ve always attempted to make it.</p>]]></content:encoded>
	</item>
</channel>
</rss>
