<?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: Google Web Toolkit</title>
	<atom:link href="http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/</link>
	<description>I am not an IP address! I am a free 'blog!</description>
	<pubDate>Tue, 06 Jan 2009 20:26:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: robin</title>
		<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/comment-page-1/#comment-36</link>
		<dc:creator>robin</dc:creator>
		<pubDate>Tue, 01 Aug 2006 01:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/#comment-36</guid>
		<description>@Rajesh: I was going to make the same points, but didn't get around to it.

In fact (well, unverified, from memory, fact), Java and JS syntax comes from C, which comes from Algol-60. Also, the way they do objects is &lt;i&gt;totally&lt;/i&gt; different. Java uses the class-object way of doing things (such as Smalltalk does), whereas JS uses a prototype-object model. I don't consider this a relationship either :)

As for your other points, I think you're quite correct.</description>
		<content:encoded><![CDATA[<p>@Rajesh: I was going to make the same points, but didn&#8217;t get around to it.</p>
<p>In fact (well, unverified, from memory, fact), Java and JS syntax comes from C, which comes from Algol-60. Also, the way they do objects is <i>totally</i> different. Java uses the class-object way of doing things (such as Smalltalk does), whereas JS uses a prototype-object model. I don&#8217;t consider this a relationship either <img src='http://www.kallisti.net.nz/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>As for your other points, I think you&#8217;re quite correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajesh Sharma</title>
		<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/comment-page-1/#comment-35</link>
		<dc:creator>Rajesh Sharma</dc:creator>
		<pubDate>Tue, 01 Aug 2006 01:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/#comment-35</guid>
		<description>I just can't help but get sracastic w.r.t to the above comment.

"Most Javascript's syntax and some of its semantics were taken from Java"

That would mean C# and some of the new breed of OOP languages are ALSO RELATED to Java. Sure.

"Java and Javascript are both used to make interactive web applications"

And so is Perl, Python, Ruby, etc etc. I guess they are ALSO RELATED to Java. Absolutely!

"A Javascript interpreter is bundled with Java 6.0"

Now that is a strong relationship! Unfortunately its still not a reality!

"Java and Javascript are both programming languages"

And so is all the other 15, 234.5 programming languages out there!</description>
		<content:encoded><![CDATA[<p>I just can&#8217;t help but get sracastic w.r.t to the above comment.</p>
<p>&#8220;Most Javascript&#8217;s syntax and some of its semantics were taken from Java&#8221;</p>
<p>That would mean C# and some of the new breed of OOP languages are ALSO RELATED to Java. Sure.</p>
<p>&#8220;Java and Javascript are both used to make interactive web applications&#8221;</p>
<p>And so is Perl, Python, Ruby, etc etc. I guess they are ALSO RELATED to Java. Absolutely!</p>
<p>&#8220;A Javascript interpreter is bundled with Java 6.0&#8243;</p>
<p>Now that is a strong relationship! Unfortunately its still not a reality!</p>
<p>&#8220;Java and Javascript are both programming languages&#8221;</p>
<p>And so is all the other 15, 234.5 programming languages out there!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Lea</title>
		<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/comment-page-1/#comment-32</link>
		<dc:creator>Keith Lea</dc:creator>
		<pubDate>Thu, 20 Jul 2006 01:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/#comment-32</guid>
		<description>You said "Java and Javascript are in no way related, except for the unfortunate confusing similarity in name." This is incorrect. Java and Javascript are related in the following ways:

- Most of Javascript's syntax and some of its semantics were taken from Java
- Java and Javascript are both used to make interactive web applications
- A Javascript interpreter is bundled with Java 6.0
- Java and Javascript are both programming languages</description>
		<content:encoded><![CDATA[<p>You said &#8220;Java and Javascript are in no way related, except for the unfortunate confusing similarity in name.&#8221; This is incorrect. Java and Javascript are related in the following ways:</p>
<p>- Most of Javascript&#8217;s syntax and some of its semantics were taken from Java<br />
- Java and Javascript are both used to make interactive web applications<br />
- A Javascript interpreter is bundled with Java 6.0<br />
- Java and Javascript are both programming languages</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robin</title>
		<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/comment-page-1/#comment-31</link>
		<dc:creator>robin</dc:creator>
		<pubDate>Mon, 17 Jul 2006 08:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/#comment-31</guid>
		<description>Strictly and pedantically speaking, it's not ECMAScript, it's JavaScript. They're not the same thing, ECMAScript is a superset, and JS contains things as standard that aren't present in ECMAScript, e.g. DOM manipulation stuff.</description>
		<content:encoded><![CDATA[<p>Strictly and pedantically speaking, it&#8217;s not ECMAScript, it&#8217;s JavaScript. They&#8217;re not the same thing, ECMAScript is a superset, and JS contains things as standard that aren&#8217;t present in ECMAScript, e.g. DOM manipulation stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tikitu</title>
		<link>http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/comment-page-1/#comment-30</link>
		<dc:creator>tikitu</dc:creator>
		<pubDate>Mon, 17 Jul 2006 08:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.kallisti.net.nz/blog/2006/07/google-web-toolkit/#comment-30</guid>
		<description>Want to sound like a real geek? Call it &lt;a href="http://en.wikipedia.org/wiki/ECMAScript" rel="nofollow"&gt;ECMAScript&lt;/a&gt;. ^_^</description>
		<content:encoded><![CDATA[<p>Want to sound like a real geek? Call it <a href="http://en.wikipedia.org/wiki/ECMAScript" rel="nofollow">ECMAScript</a>. ^_^</p>
]]></content:encoded>
	</item>
</channel>
</rss>
