Google I/O: Google App Engine fireside chat
There were a few questions about the choice of Python as a language, and whether and what languages would come next, comparisons to other existing containers, and so forth. Guido van Rossum said it was partly because Python is one of the three big languages at Google, and because it was (relatively) easy to harden the VM. Kevin Gibbs said they had to start somewhere, and that they were committed to others. Paul McDonald said that the two most voted-for issues on the issue tracker are language-related, and that there were teams (ie, more than one) currently actively working on languages (ie, more than one).
A couple of questions around "maturity" - the team says they'll make it clear when it is no longer a preview, and that this will probably happen when they have the billing set up and offline processing. They expect billing to be available "toward the end of the year".
Question about HTTPS/SSL and access to encryption within GAE code. Answer is that it's something they want to do, but don't know when they'll get to it. Data is "strictly" partitioned between apps in the store (BigTable).
A common thread in answers were that the Google App Engine team were very interested in people being able to get their data and code out of GAE, and they're working on making it easy to bulk output the data. They hoped that a standard would emerge for BigTable-like storage (CouchDB, SimpleDB) so that people could write code and host it on GAE or elsewhere. And people are already working on compatible APIs to make it possible to run on other storage systems (but may not be too efficient).