<?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: Comparing the evolution of Java and JavaScript</title>
	<atom:link href="http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260232</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Fri, 21 Dec 2007 00:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260232</guid>
		<description>In case it wasn&#039;t clear, my point about IE alert was not that it is a good example of classes -- but it does show they intrude into JS already. There are great examples where you do want a hardened little instance that can be efficiently created by the millions, can&#039;t be tampered with at all, can be used as an unforgeable capability, etc. Classes as conceived in JS2 have their uses.

/be</description>
		<content:encoded><![CDATA[<p>In case it wasn&#8217;t clear, my point about IE alert was not that it is a good example of classes &#8212; but it does show they intrude into JS already. There are great examples where you do want a hardened little instance that can be efficiently created by the millions, can&#8217;t be tampered with at all, can be used as an unforgeable capability, etc. Classes as conceived in JS2 have their uses.</p>
<p>/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260231</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Thu, 20 Dec 2007 23:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260231</guid>
		<description>Of course JS is not turning into Java, Joe spoke to that.

Here&#039;s the thing about your very example: alert is a function object, right? Wrong, in IE -- it&#039;s a &quot;host object&quot;, an instance of a &quot;class&quot; you can&#039;t make or extend. It has no apply or call method delegated to Function.prototype.

Give the &lt;a href=&quot;http://www.ecmascript.org/es4/spec/evolutionary-programming-tutorial.pdf&quot; rel=&quot;nofollow&quot;&gt;ES4 evolutionary programming tutorial&lt;/a&gt; a read if you haven&#039;t yet. Nothing like Java -- way better ;-).

/be</description>
		<content:encoded><![CDATA[<p>Of course JS is not turning into Java, Joe spoke to that.</p>
<p>Here&#8217;s the thing about your very example: alert is a function object, right? Wrong, in IE &#8212; it&#8217;s a &#8220;host object&#8221;, an instance of a &#8220;class&#8221; you can&#8217;t make or extend. It has no apply or call method delegated to Function.prototype.</p>
<p>Give the <a href="http://www.ecmascript.org/es4/spec/evolutionary-programming-tutorial.pdf" rel="nofollow">ES4 evolutionary programming tutorial</a> a read if you haven&#8217;t yet. Nothing like Java &#8212; way better ;-).</p>
<p>/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McLars</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260211</link>
		<dc:creator>McLars</dc:creator>
		<pubDate>Thu, 20 Dec 2007 15:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260211</guid>
		<description>I agree that browser disparities (deficiencies?) should not halt JS evolution. The question is in which direction JS should be evolving, more complex or simpler. I think the recent explosion in frameworks/libraries indicates that people want simpler interfaces. Simple does not exclude greater power. For example, when you can select a whole group of elements with just a $() or $$() statement, that saves a ton of work and makes the code easiert to read and maintain. I&#039;m all for making that sort of power native to JS. I&#039;m just against making it harder to learn and use day-to-day. My worst nightmare would be requiring people to follow a complicated class structure just to pop up an alert. Again, there are plenty of industrial-strength, fully-compiled languages out there. Maybe more work needs to be done to get those implemented better on the browser. But JS is the only thing we have for low-level, simple scripting tasks. You can make it more powerful, yes, but please don&#039;t turn it into Java.</description>
		<content:encoded><![CDATA[<p>I agree that browser disparities (deficiencies?) should not halt JS evolution. The question is in which direction JS should be evolving, more complex or simpler. I think the recent explosion in frameworks/libraries indicates that people want simpler interfaces. Simple does not exclude greater power. For example, when you can select a whole group of elements with just a $() or $$() statement, that saves a ton of work and makes the code easiert to read and maintain. I&#8217;m all for making that sort of power native to JS. I&#8217;m just against making it harder to learn and use day-to-day. My worst nightmare would be requiring people to follow a complicated class structure just to pop up an alert. Again, there are plenty of industrial-strength, fully-compiled languages out there. Maybe more work needs to be done to get those implemented better on the browser. But JS is the only thing we have for low-level, simple scripting tasks. You can make it more powerful, yes, but please don&#8217;t turn it into Java.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260189</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Thu, 20 Dec 2007 00:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260189</guid>
		<description>dmdevito: a great idea, often suggested and discussed, even in the hearing of Google folks in the open source group there.

McLars: the disparity between browsers is mainly outside of JS -- and where JS disparities hurt, you-know-who is the most behind (hint: who just patched JScript&#039;s DLL for IE6).

Platform disparities are no excuse for halting the evolution of the web standards, including JS. It&#039;s not as if we haven&#039;t had years for the weaker JS implementations (never mind CSS and DOM) to catch up. Look to competitive pressure, or lack of it, to explain progress or stagnation.

/be</description>
		<content:encoded><![CDATA[<p>dmdevito: a great idea, often suggested and discussed, even in the hearing of Google folks in the open source group there.</p>
<p>McLars: the disparity between browsers is mainly outside of JS &#8212; and where JS disparities hurt, you-know-who is the most behind (hint: who just patched JScript&#8217;s DLL for IE6).</p>
<p>Platform disparities are no excuse for halting the evolution of the web standards, including JS. It&#8217;s not as if we haven&#8217;t had years for the weaker JS implementations (never mind CSS and DOM) to catch up. Look to competitive pressure, or lack of it, to explain progress or stagnation.</p>
<p>/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McLars</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260179</link>
		<dc:creator>McLars</dc:creator>
		<pubDate>Wed, 19 Dec 2007 22:54:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260179</guid>
		<description>It often seems people read the first four letters and skip the rest of the name. It is a scripting language. There&#039;s no shortage of complex languages and tools for the uber-geeks, but there&#039;s also a need for simple scripting. And given the current disparity between browser implementations, do you think increasing the complexity of Javascript would make it more or less reliable, cross-browser? We shouldn&#039;t even need all these frameworks and libraries. It&#039;s just another layer of code and a whole new &quot;language&quot; to learn, in addition to Javascript. Fix the basics before you worry about expanding the scope.</description>
		<content:encoded><![CDATA[<p>It often seems people read the first four letters and skip the rest of the name. It is a scripting language. There&#8217;s no shortage of complex languages and tools for the uber-geeks, but there&#8217;s also a need for simple scripting. And given the current disparity between browser implementations, do you think increasing the complexity of Javascript would make it more or less reliable, cross-browser? We shouldn&#8217;t even need all these frameworks and libraries. It&#8217;s just another layer of code and a whole new &#8220;language&#8221; to learn, in addition to Javascript. Fix the basics before you worry about expanding the scope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dmdevito</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260178</link>
		<dc:creator>dmdevito</dc:creator>
		<pubDate>Wed, 19 Dec 2007 22:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260178</guid>
		<description>While reading this post and questioning myself the evolution of JS, I am wondering if JS needs a more standard library like Java (a CPAN web site ?). Let me give an example. AFAIK GWT translates java.util package classes into JS. OK, the compiler could optimize it while translating only needed classes. But why not having a more or less standard JS library published on a Google high-speed web site so that the compiler could rely on it and the browsers could download it once for all web sites using this standard library ?</description>
		<content:encoded><![CDATA[<p>While reading this post and questioning myself the evolution of JS, I am wondering if JS needs a more standard library like Java (a CPAN web site ?). Let me give an example. AFAIK GWT translates java.util package classes into JS. OK, the compiler could optimize it while translating only needed classes. But why not having a more or less standard JS library published on a Google high-speed web site so that the compiler could rely on it and the browsers could download it once for all web sites using this standard library ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vance Dubberly</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260174</link>
		<dc:creator>vance Dubberly</dc:creator>
		<pubDate>Wed, 19 Dec 2007 17:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260174</guid>
		<description>Ya know I&#039;m watching AS developers move from AS2 to AS3 which from what I gather is going to be somewhat akin to moving to Javscript 2.  To be honest, I can&#039;t wait. I&#039;ve watched an endless amount of bungled impossible to follow code suddenly become legible, reusable, and easy to debug.    Yes in AS2 simple things were easier to do, just as they are in our current JS world but adding some structure made the really hard things a lot easier.</description>
		<content:encoded><![CDATA[<p>Ya know I&#8217;m watching AS developers move from AS2 to AS3 which from what I gather is going to be somewhat akin to moving to Javscript 2.  To be honest, I can&#8217;t wait. I&#8217;ve watched an endless amount of bungled impossible to follow code suddenly become legible, reusable, and easy to debug.    Yes in AS2 simple things were easier to do, just as they are in our current JS world but adding some structure made the really hard things a lot easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dcrec1</title>
		<link>http://ajaxian.com/archives/comparing-the-evolution-of-java-and-javascript/comment-page-1#comment-260160</link>
		<dc:creator>dcrec1</dc:creator>
		<pubDate>Wed, 19 Dec 2007 13:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=3129#comment-260160</guid>
		<description>Excellent post!</description>
		<content:encoded><![CDATA[<p>Excellent post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

