<?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 1.2 Uses WebKit</title>
	<atom:link href="http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/feed/" rel="self" type="application/rss+xml" />
	<link>http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/</link>
	<description>All about WebKit development</description>
	<lastBuildDate>Sat, 21 Nov 2009 23:00:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jeff Schiller</title>
		<link>http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/comment-page-1/#comment-13169</link>
		<dc:creator>Jeff Schiller</dc:creator>
		<pubDate>Tue, 21 Nov 2006 22:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/?p=81#comment-13169</guid>
		<description>Google realizes that the situation we are in with web development right now is similar to the situation that early developers faced when having to port applications between processors - you have to contend with each (virtual) machine&#039;s idiosyncracies, levels of support, bugs, etc.  That&#039;s why higher level languages were invented - to abstract those niggling details and way and let developers be more productive.

And Google&#039;s not alone.  Sun, Adobe, Dojo, OpenLaszlo and even Microsoft (Atlas) all realize that we need to &quot;move up the stack&quot; in web development to get away from all this browser compatibility ridiculousness.</description>
		<content:encoded><![CDATA[<p>Google realizes that the situation we are in with web development right now is similar to the situation that early developers faced when having to port applications between processors &#8211; you have to contend with each (virtual) machine&#8217;s idiosyncracies, levels of support, bugs, etc.  That&#8217;s why higher level languages were invented &#8211; to abstract those niggling details and way and let developers be more productive.</p>
<p>And Google&#8217;s not alone.  Sun, Adobe, Dojo, OpenLaszlo and even Microsoft (Atlas) all realize that we need to &#8220;move up the stack&#8221; in web development to get away from all this browser compatibility ridiculousness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nickfitz</title>
		<link>http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/comment-page-1/#comment-13108</link>
		<dc:creator>nickfitz</dc:creator>
		<pubDate>Mon, 20 Nov 2006 14:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/?p=81#comment-13108</guid>
		<description>It&#039;s always struck me as bizarre that Google think this is a good idea. If you want to help people to write JavaScript applications, surely it would be rather more useful if they were written in, oh, I don&#039;t know... JavaScript?</description>
		<content:encoded><![CDATA[<p>It&#8217;s always struck me as bizarre that Google think this is a good idea. If you want to help people to write JavaScript applications, surely it would be rather more useful if they were written in, oh, I don&#8217;t know&#8230; JavaScript?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myrd</title>
		<link>http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/comment-page-1/#comment-13074</link>
		<dc:creator>Myrd</dc:creator>
		<pubDate>Sat, 18 Nov 2006 16:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://webkit.org/blog/?p=81#comment-13074</guid>
		<description>Nice</description>
		<content:encoded><![CDATA[<p>Nice</p>
]]></content:encoded>
	</item>
</channel>
</rss>
