<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Google App Engine</title>
	<link>http://efford.org/blog/archives/37</link>
	<description>Random musings on Python, software engineering, the web &#038; other stuff</description>
	<pubDate>Thu, 11 Mar 2010 21:45:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Nodalities &#187; Blog Archive &#187; Google App Engine and the Joy of WebArch</title>
		<link>http://efford.org/blog/archives/37#comment-31732</link>
		<pubDate>Thu, 17 Apr 2008 16:51:08 +0000</pubDate>
		<guid>http://efford.org/blog/archives/37#comment-31732</guid>
					<description>[...] Responses to the announcement of the Google App Engine have been mixed, from Tim Bray&#8217;s somewhat negative Sharecropping, to an awful lot of &#8220;very cool&#8220;s, with Niall Kennedy&#8217;s tech description providing a reasonably neutral common ground. I&#8217;ve been meaning to post about it, but I&#8217;ve a couple of pressing deadlines and haven&#8217;t had time. I didn&#8217;t think &#8220;Python - great! But this thing really isn&#8217;t forward-looking&#8221; would be doing it justice. However this morning I ran across a couple of blog posts on which I felt obliged to comment, and I just realised that most of my main points about the Google App Engine leaked out into those comments. So with apologies in lieu of better treatment, here goes - [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Responses to the announcement of the Google App Engine have been mixed, from Tim Bray&#8217;s somewhat negative Sharecropping, to an awful lot of &#8220;very cool&#8220;s, with Niall Kennedy&#8217;s tech description providing a reasonably neutral common ground. I&#8217;ve been meaning to post about it, but I&#8217;ve a couple of pressing deadlines and haven&#8217;t had time. I didn&#8217;t think &#8220;Python - great! But this thing really isn&#8217;t forward-looking&#8221; would be doing it justice. However this morning I ran across a couple of blog posts on which I felt obliged to comment, and I just realised that most of my main points about the Google App Engine leaked out into those comments. So with apologies in lieu of better treatment, here goes - [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
