<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Should Adobe follow the new ECMAScript 3.1 standard?</title>
	<atom:link href="http://natejc.com/blog/2008/08/should-adobe-follow-the-new-ecmascript-31-standard/feed/" rel="self" type="application/rss+xml" />
	<link>http://natejc.com/blog/2008/08/should-adobe-follow-the-new-ecmascript-31-standard/</link>
	<description>Flash &#038; ActionScript 3 info, source, &#038; experiments</description>
	<lastBuildDate>Sun, 07 Feb 2010 10:49:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Danny Miller</title>
		<link>http://natejc.com/blog/2008/08/should-adobe-follow-the-new-ecmascript-31-standard/comment-page-1/#comment-51930</link>
		<dc:creator>Danny Miller</dc:creator>
		<pubDate>Sat, 16 Aug 2008 11:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://natejc.com/blog/?p=97#comment-51930</guid>
		<description>&quot;The only time I ever wish that various rich oop languages were more “standardized” is when one language has a really nice feature/ability that I become dependent on, and then I switch to another rich oop language that doesn’t support it. For example, there are many times that I have griped that I wish AS supported all of the features that usually come “standard” in other rich oop languages, such as private constructors, function overloading, strongly typed arrays (vectors), etc. ActionScript 3 was a big step in the right direction and I thought ES4 would solve most of my remaining gripes.&quot;


I completely 100% agree with this paragraph. 

&quot;My view, however, implies that a standard in the programming world is used to set the *minimum* feature set that a language has, NOT the maximum.&quot;

I think you&#039;re right in this paragraph but it depends on what we&#039;re talking about.

In my opinion, the biggest misconception is that the same criticsm of standards applies to coding literature as it does to others things (browsers, UI, color schemes, etc).

Read my article: http://k2xl.com/wordpress/2008/08/15/web-standards/</description>
		<content:encoded><![CDATA[<p>&#8220;The only time I ever wish that various rich oop languages were more “standardized” is when one language has a really nice feature/ability that I become dependent on, and then I switch to another rich oop language that doesn’t support it. For example, there are many times that I have griped that I wish AS supported all of the features that usually come “standard” in other rich oop languages, such as private constructors, function overloading, strongly typed arrays (vectors), etc. ActionScript 3 was a big step in the right direction and I thought ES4 would solve most of my remaining gripes.&#8221;</p>
<p>I completely 100% agree with this paragraph. </p>
<p>&#8220;My view, however, implies that a standard in the programming world is used to set the *minimum* feature set that a language has, NOT the maximum.&#8221;</p>
<p>I think you&#8217;re right in this paragraph but it depends on what we&#8217;re talking about.</p>
<p>In my opinion, the biggest misconception is that the same criticsm of standards applies to coding literature as it does to others things (browsers, UI, color schemes, etc).</p>
<p>Read my article: <a href="http://k2xl.com/wordpress/2008/08/15/web-standards/" rel="nofollow">http://k2xl.com/wordpress/2008/08/15/web-standards/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
