<?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: The Effects of ECMAScript 4&#8242;s Abandonment on Pedagogy of Rich Media Development Languages</title>
	<atom:link href="http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/feed/" rel="self" type="application/rss+xml" />
	<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/</link>
	<description>Design, Development, Technology and My Life.</description>
	<lastBuildDate>Tue, 27 Dec 2011 16:30:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Chad</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52631</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Sat, 16 Aug 2008 13:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52631</guid>
		<description>@Lars,

Thanks for the comments and the clarifications on WaSP. I appreciate being set straight!</description>
		<content:encoded><![CDATA[<p>@Lars,</p>
<p>Thanks for the comments and the clarifications on WaSP. I appreciate being set straight!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Gunther</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52619</link>
		<dc:creator>Lars Gunther</dc:creator>
		<pubDate>Sat, 16 Aug 2008 07:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52619</guid>
		<description>@Doug C:

I&#039;ve heard that class-based objects are critical to speed on mobile platforms. Even if they are not off the table for Harmony, they for sure have been postponed and that is a *substantive* loss - even if they can be emulated using protype based inheritance.

Speaking from a pedagogic point of view, they are also very nice when teaching ECMAScript to serve as a bridge between languages.</description>
		<content:encoded><![CDATA[<p>@Doug C:</p>
<p>I&#8217;ve heard that class-based objects are critical to speed on mobile platforms. Even if they are not off the table for Harmony, they for sure have been postponed and that is a *substantive* loss &#8211; even if they can be emulated using protype based inheritance.</p>
<p>Speaking from a pedagogic point of view, they are also very nice when teaching ECMAScript to serve as a bridge between languages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Gunther</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52618</link>
		<dc:creator>Lars Gunther</dc:creator>
		<pubDate>Sat, 16 Aug 2008 07:11:24 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52618</guid>
		<description>For the record. W3C and WaSP are separate entities. W3C has no &quot;Dreamweaver Task Force&quot;. WaSP had. It is now renamed &quot;Adobe Task Force&quot;. (I am a member of the Educational task Force.)

WaSP had a DOM Scripting Task force, but is is not active anymore. Its purpose was to educate about best practices (unobtrusiveness, capability testing, progressive enhancement, etc) and was not charged with working on the specs.

WaSP is more about helping browser and tool vendors implement the specs and the general public following them when developing web sites.</description>
		<content:encoded><![CDATA[<p>For the record. W3C and WaSP are separate entities. W3C has no &#8220;Dreamweaver Task Force&#8221;. WaSP had. It is now renamed &#8220;Adobe Task Force&#8221;. (I am a member of the Educational task Force.)</p>
<p>WaSP had a DOM Scripting Task force, but is is not active anymore. Its purpose was to educate about best practices (unobtrusiveness, capability testing, progressive enhancement, etc) and was not charged with working on the specs.</p>
<p>WaSP is more about helping browser and tool vendors implement the specs and the general public following them when developing web sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Crockford</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52607</link>
		<dc:creator>Douglas Crockford</dc:creator>
		<pubDate>Sat, 16 Aug 2008 00:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52607</guid>
		<description></description>
		<content:encoded><![CDATA[<p>This statement, &#8220;it‚Äôs only fitting that the behavioral layer‚Äôs future get neutered in order to serve MS and stagnate the web again,&#8221; appears to be based on some misinformation. Let me set the record straight. ES4 had a very long and extensive feature list, but it did not include testicles or any other form of genitalia. It had a lot of other stuff, but somehow it didn&#8217;t have that. The features its did have would not have allowed you to do anything that you won&#8217;t be able be able to do in ES3.1. You have not lost anything substantive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RansomWeaver</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52606</link>
		<dc:creator>RansomWeaver</dc:creator>
		<pubDate>Sat, 16 Aug 2008 00:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52606</guid>
		<description>What about a sniffer that demands flash player when it detects something other than Firefox? That&#039;s no worse than where we&#039;re at today.... If the flash player can load content written for Mozilla Tamarin, It puts the onus on the browser devs to bring their product up to standard or fall behind.</description>
		<content:encoded><![CDATA[<p>What about a sniffer that demands flash player when it detects something other than Firefox? That&#8217;s no worse than where we&#8217;re at today&#8230;. If the flash player can load content written for Mozilla Tamarin, It puts the onus on the browser devs to bring their product up to standard or fall behind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry B. Garland</title>
		<link>http://visualrinse.com/2008/08/15/the-effects-of-ecmascript-4s-abandonment-on-pedagogy-of-rich-media-development-languages/comment-page-1/#comment-52590</link>
		<dc:creator>Harry B. Garland</dc:creator>
		<pubDate>Fri, 15 Aug 2008 20:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://visualrinse.com/?p=399#comment-52590</guid>
		<description>What if Mozilla and Adobe both implement Tamerin anyway?  You could just tell developers that if they are willing to create a Firefox-only web application, they can use a much better language than the one used by Internet Explorer and Safari?  Why should everybody suffer just because 2 companies are too big and political to innovate?</description>
		<content:encoded><![CDATA[<p>What if Mozilla and Adobe both implement Tamerin anyway?  You could just tell developers that if they are willing to create a Firefox-only web application, they can use a much better language than the one used by Internet Explorer and Safari?  Why should everybody suffer just because 2 companies are too big and political to innovate?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

