<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: App Engine and Pylons</title>
	<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/</link>
	<description></description>
	<pubDate>Wed, 09 Jul 2008 12:10:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Iain Duncan</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16819</link>
		<dc:creator>Iain Duncan</dc:creator>
		<pubDate>Fri, 18 Apr 2008 20:20:24 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16819</guid>
		<description>Whether or not you would use it, getting platforms working on App engine is going to have a huge trickle down effect on python web dev. Right now deployment is the biggest hurdle to wider adoption, and if Google is providing free deployment with a good tool set, you can bet that way more people will be trying python out for web dev, resulting in community growth, and all the major hosting companies are going to have to start paying attention to python or lose out.  From a python growth and marketing perspective, app engine is great news and the work put into getting the major platforms working is well worth it!

Thanks!</description>
		<content:encoded><![CDATA[<p>Whether or not you would use it, getting platforms working on App engine is going to have a huge trickle down effect on python web dev. Right now deployment is the biggest hurdle to wider adoption, and if Google is providing free deployment with a good tool set, you can bet that way more people will be trying python out for web dev, resulting in community growth, and all the major hosting companies are going to have to start paying attention to python or lose out.  From a python growth and marketing perspective, app engine is great news and the work put into getting the major platforms working is well worth it!</p>

<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16733</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Mon, 14 Apr 2008 22:36:48 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16733</guid>
		<description>Ken: no hosting is free.  To start out with this is the cheapest hosting out there (free!) -- we don't know how the charges will look after that.  But I would be surprised if it didn't stay the cheapest.

Asbjørn: the Datastore doesn't have locking, but it does have transactions.  Filesystems don't usually have transactions, but they do have locking.  While it would kind of work, it seems awkward, and it would perform so differently from a real filesystem that I think it wouldn't work very well.</description>
		<content:encoded><![CDATA[<p>Ken: no hosting is free.  To start out with this is the cheapest hosting out there (free!) &#8212; we don&#8217;t know how the charges will look after that.  But I would be surprised if it didn&#8217;t stay the cheapest.</p>

<p>Asbjørn: the Datastore doesn&#8217;t have locking, but it does have transactions.  Filesystems don&#8217;t usually have transactions, but they do have locking.  While it would kind of work, it seems awkward, and it would perform so differently from a real filesystem that I think it wouldn&#8217;t work very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Fowler</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16729</link>
		<dc:creator>Ken Fowler</dc:creator>
		<pubDate>Mon, 14 Apr 2008 20:14:47 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16729</guid>
		<description>IIRC, once you have to scale up, then you have to start getting charged extra.  So then you are paying just like you would somewhere else, except you are married to google's sandbox?  if that is true, then no thanks.</description>
		<content:encoded><![CDATA[<p>IIRC, once you have to scale up, then you have to start getting charged extra.  So then you are paying just like you would somewhere else, except you are married to google&#8217;s sandbox?  if that is true, then no thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Martindale</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16726</link>
		<dc:creator>Eric Martindale</dc:creator>
		<pubDate>Mon, 14 Apr 2008 18:17:42 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16726</guid>
		<description>Obligatory "Need to construct more Pylons" comment.</description>
		<content:encoded><![CDATA[<p>Obligatory &#8220;Need to construct more Pylons&#8221; comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asbjørn Ulsberg</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16725</link>
		<dc:creator>Asbjørn Ulsberg</dc:creator>
		<pubDate>Mon, 14 Apr 2008 10:29:54 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16725</guid>
		<description>I wonder why file system stuff isn't implemented atop of Big Table. How hard is it to just dump the file inside the database, and then retrieve it with the file path as the key? It's okay that GAE has restrictions, but they should replace all standard libraries with their own alternatives, perhaps even transparently where possible.</description>
		<content:encoded><![CDATA[<p>I wonder why file system stuff isn&#8217;t implemented atop of Big Table. How hard is it to just dump the file inside the database, and then retrieve it with the file path as the key? It&#8217;s okay that GAE has restrictions, but they should replace all standard libraries with their own alternatives, perhaps even transparently where possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16716</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Sun, 13 Apr 2008 23:13:17 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16716</guid>
		<description>The manageability is as important to me as the price.  People time is expensive, so why waste it managing servers?  (Personally the manageability of the environment is more attractive than the scalability, though the two are of course related)</description>
		<content:encoded><![CDATA[<p>The manageability is as important to me as the price.  People time is expensive, so why waste it managing servers?  (Personally the manageability of the environment is more attractive than the scalability, though the two are of course related)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16715</link>
		<dc:creator>Kurt</dc:creator>
		<pubDate>Sun, 13 Apr 2008 23:03:57 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16715</guid>
		<description>Well, the advantage of the Google thing isn't necessarily the price.  It's the ability to scale an application until the sky turns plaid.  

A good chunk of the effort is similar to the effort you'd have to put in to handle gobs of traffic.  With the AppEngine, though, you don't have to do anything but write your application intelligently.  They handle all the repetitive annoying stuff.</description>
		<content:encoded><![CDATA[<p>Well, the advantage of the Google thing isn&#8217;t necessarily the price.  It&#8217;s the ability to scale an application until the sky turns plaid.  </p>

<p>A good chunk of the effort is similar to the effort you&#8217;d have to put in to handle gobs of traffic.  With the AppEngine, though, you don&#8217;t have to do anything but write your application intelligently.  They handle all the repetitive annoying stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Kelly</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16714</link>
		<dc:creator>Christopher Kelly</dc:creator>
		<pubDate>Sun, 13 Apr 2008 22:45:50 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16714</guid>
		<description>Am I missing something about this App Engine? People time is expensive, computers are cheap, right? Why would you go to all this effort to port to a free hosting platform when it's virtually free anyway? I pay $30 a month for dedicated Linux box from [server pronto](http://www.serverpronto.com/) and it's great.</description>
		<content:encoded><![CDATA[<p>Am I missing something about this App Engine? People time is expensive, computers are cheap, right? Why would you go to all this effort to port to a free hosting platform when it&#8217;s virtually free anyway? I pay $30 a month for dedicated Linux box from <a href="http://www.serverpronto.com/">server pronto</a> and it&#8217;s great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Jenvey</title>
		<link>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16705</link>
		<dc:creator>Philip Jenvey</dc:creator>
		<pubDate>Sun, 13 Apr 2008 20:56:20 +0000</pubDate>
		<guid>http://blog.ianbicking.org/2008/04/13/app-engine-and-pylons/#comment-16705</guid>
		<description>I'll also note that Ben Bangert has just released a new version of [Beaker](http://pypi.python.org/pypi/Beaker/0.9.4) that adds support for sessions and caches backed by [Google App Engine's Datastore API](http://code.google.com/appengine/docs/datastore/).</description>
		<content:encoded><![CDATA[<p>I&#8217;ll also note that Ben Bangert has just released a new version of <a href="http://pypi.python.org/pypi/Beaker/0.9.4">Beaker</a> that adds support for sessions and caches backed by <a href="http://code.google.com/appengine/docs/datastore/">Google App Engine&#8217;s Datastore API</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
