Google I / O

On May 28–29, a Google I / O developer meeting was held in San Francisco.
The range of topics covered was quite wide: the Android mobile platform, Open Social, the new App Engine, all sorts of web-based client technologies (including AJAX) and much more; I will just describe a couple of points about App Engine.

For example, Offermann.us writes :

Use Django. Do not use the one included in App Engine (version 0.96). Yes, get a fresh development-version of Django 0.97 from the repository. And what is interesting: despite the fact that Google App Engine comes with a webapp framework and Django 0.96, Guido van Rossum devoted his speech to how to install and use Django 0.97 on Google Application Engine. I was curious about what the webapp was meant for, so I asked him the question: does it make sense to use it instead of Django. Guido replied that the webapp is simple and allows you to run something very quickly. But Django is more powerful.

Do not use count (). Never. (In Django, count () is a method that performs a SELECT COUNT (*) query on a database.) This has been highlighted in several presentations. Not only because it does not count more than a thousand , but also requires an analysis of each entity, which requires too much computing power.

And from the same interesting quotation:

In his presentation on how Datastore (the database interface provided by AppEngine) works from the inside, Ryan Barrett casually mentioned three significant priorities for the Google App Engine team in the near future:

1. Import and export data
2. Additional languages
3. Billing system

')
Unfortunately, the official Google I / O page is still in an obsolete state, and I could not find somewhere normal abstracts / presentations.